Hermes Task Instructions

tell me what I should instruct hermes to do next in order to advance my interests

Based on where your site is now and what you've been trying to accomplish over the last few days, I would stop polishing the visual design and start building assets that compound over time. Your goal isn't just to have a nice portfolio—it's to convert readers into opportunities (jobs, consulting, collaborations, book sales, newsletter subscribers, and eventually software customers). The next thing I'd have Hermes build is a **proper research hub**. ### Prompt for Hermes > Redesign the Research section into the central knowledge hub of the website. > > Goals: > > - Organize all articles into research categories instead of a chronological blog. > - Categories should include AI Engineering, Multi-Agent Systems, RAG, Knowledge Graphs, Cognitive Architectures, Software Engineering, Philosophy of AI, and Essays. > - Every article should have: > - estimated reading time > - publication date > - tags > - previous/next navigation > - related articles based on tags > - a table of contents > - social sharing buttons > - canonical URLs and structured data > - Add a featured article section at the top containing cornerstone articles. > - Add an "Essential Reading" section for first-time visitors. > - Add a search bar that searches all articles instantly. > - Add filtering by category and tags. > - Make article cards much more information dense while remaining clean. > - Add article series support so related posts can be grouped together. > - Improve typography for long-form technical reading. > - Add an author box after every article with links to Projects, About, and the book. > - Add newsletter signup after every article. > - Improve SEO metadata throughout. > - Ensure the entire page performs well on mobile. --- After that, I think the biggest missing piece on your site is **evidence**. Right now visitors see a lot of ideas, but relatively little proof that you've built substantial systems. I'd have Hermes create detailed project pages for your strongest work. For each project, include: - What problem it solves. - Architecture diagrams. - Screenshots. - Technical stack. - Design decisions. - Performance. - Challenges encountered. - Lessons learned. - GitHub links. - Live demos where possible. Someone evaluating you for an engineering role should be able to spend 15 minutes on your site and think, *"This person has actually built interesting systems."* After that, I'd build an **AI Lab** section. This would showcase your experiments in a way that encourages repeat visits. Include: - Interactive demos. - Architecture visualizations. - Embedding explorers. - Persona demonstrations. - Retrieval visualizations. - Knowledge graph explorers. - Model comparison pages. Finally, I'd create a **conversion layer** across the site. Every page should answer the question, "What should this visitor do next?" Add clear calls to action such as: - Download the book. - Read the essential articles. - Explore the projects. - Contact you. - Subscribe for updates. - View GitHub. One broader observation from reviewing your recent iterations is that you're approaching the point where adding more visual polish will have diminishing returns. The biggest gains now will come from making your work easier to understand, navigate, and trust. High-quality organization, richer project documentation, and stronger evidence of your engineering work are likely to do more for your long-term goals than another redesign of the homepage.

how about you give me a series of coding agent prompts to iteratively enter so that I can see the results before progressing to each stage

I think that's a better approach. One giant prompt tends to make an AI coding agent change too many things at once. If you iterate, you can evaluate each improvement before moving on. I'd use something like this roadmap. --- ## Prompt 1 — Turn the Research page into a real knowledge hub ``` Redesign the Research page while preserving all existing content. Goals: - Stop treating it like a chronological blog. - Introduce a clean category system. - Add category cards at the top. - Add a prominent search bar. - Add tag filtering. - Add a "Featured Research" section above everything else. - Add an "Essential Reading" section immediately below Featured Research. - Improve spacing and typography. - Keep the page fast. - Make it feel like an AI research laboratory rather than a personal blog. Do not redesign the entire website yet. Only modify the Research section. ``` **Stop here. Evaluate it.** --- ## Prompt 2 — Make every article much richer ``` Improve the article template. For every article page: - Add reading time. - Add publication date. - Add tags. - Add a sticky table of contents. - Add previous/next article navigation. - Add related articles based on shared tags. - Improve code block styling. - Improve typography for long-form reading. - Add an author section at the end. - Add links to Projects and About. - Add a newsletter signup section. - Improve SEO metadata. Do not change article content. ``` Evaluate. --- ## Prompt 3 — Upgrade Projects into engineering case studies ``` Completely redesign the Projects page. Every project should feel like an engineering portfolio entry rather than a card. Each project preview should include: - summary - technologies - status - architecture highlights - links - GitHub - demo Each project should have its own detailed page containing: - Overview - Motivation - Architecture - Technical Stack - Design Decisions - Challenges - Lessons Learned - Future Work - Screenshots - Repository Links Make this comparable to the engineering portfolios of senior software engineers. ``` Evaluate. --- ## Prompt 4 — Create an AI Laboratory section ``` Create an "AI Lab" section. This is where experimental work lives. Include pages for: - Agent Architectures - RAG Experiments - Knowledge Graph Experiments - Persona Systems - Embedding Visualizations - Prompt Engineering - Local LLM Experiments Design this section as an interactive research laboratory. Use reusable components. Do not fill pages with placeholder text. ``` Evaluate. --- ## Prompt 5 — Improve the homepage ``` Redesign the homepage to communicate expertise within five seconds. Structure: Hero Mission statement Featured Research Featured Projects Book Recent Work Technologies Timeline Testimonials (if available) Call to Action Remove unnecessary text. Increase visual hierarchy. The homepage should guide visitors naturally toward the Research section and Projects. ``` Evaluate. --- ## Prompt 6 — Add architecture diagrams everywhere ``` Add interactive architecture diagrams to projects and research articles where appropriate. Use SVG or React Flow. Diagrams should illustrate: - RAG pipelines - Multi-agent systems - Knowledge graphs - Retrieval pipelines - Data flow - Persona systems They should be responsive and match the site's visual style. ``` Evaluate. --- ## Prompt 7 — Improve visual consistency ``` Audit the entire website. Improve: spacing typography card consistency button hierarchy animations hover states page transitions loading states responsive layouts Maintain the existing design language while making everything feel more polished and cohesive. Do not introduce unnecessary visual complexity. ``` Evaluate. --- ## Prompt 8 — Add credibility signals ``` Throughout the website, improve trust and credibility. Where appropriate add: publication dates GitHub links project status technology badges citations external references book links research collections Improve discoverability without clutter. Everything should reinforce that this is an active technical research site. ``` --- ## Prompt 9 — Polish performance and SEO ``` Perform a production readiness pass. Optimize: Core Web Vitals Image loading Metadata Open Graph Structured Data Accessibility Keyboard navigation ARIA labels Sitemap RSS feed Canonical URLs Bundle size Lazy loading Ensure Lighthouse scores are as high as possible without sacrificing usability. ``` --- I like this sequence because each stage delivers a meaningful, reviewable improvement. It also follows a progression from **information architecture** (organizing content), to **content presentation** (making articles and projects more compelling), to **credibility** (showing evidence of your work), and finally to **polish and optimization**. That makes it easier to catch issues early and steer the site in the direction you want instead of reviewing one massive set of changes.