portfolio_nextjs

Critique an existing developer blog post against Michael Lynch's "Refactoring English" principles and return a per-principle rubric followed by a prioritized fix list. Use whenever the user shares a draft or published post and asks for review, feedback, critique, edit, "is this any good?", "why isn't this getting traction?", "rip this apart," "review my post," or pastes a URL/markdown asking what to improve. Also trigger when a user has written a technical article, dev-log, engineering write-up, or case study and wants a quality check before publishing. Output is honest and concrete — every issue cites a specific line or section.

Write technical blog posts that developers actually read, following Michael Lynch's "Refactoring English" principles (300k+ readers/year, 30+ HN front page hits). Use whenever the user wants to draft, plan, outline, or rewrite a developer-focused blog post, dev-log entry, technical article, engineering write-up, case study, or post-mortem — even if they don't say "blog post." Trigger on phrases like "write a post about X," "turn this into an article," "draft a blog," "I want to publish," "write up my project," or pasting raw notes asking for a published version. Optimizes for skimmer-friendly structure, audience reach, and a title+intro that earns the click.

Critique a portfolio case study for a creative technologist (design + code hybrid) against six principles tuned to that role, and return a per-principle rubric followed by a prioritized fix list. Use whenever the user shares a draft or published portfolio piece, project page, case study, or "/project/<name>" page and asks for review, feedback, critique, edit, "is this any good?", "rip this apart," "review my project page," "why isn't this landing with hiring managers?", or pastes a URL/Markdown/JSX asking what to improve. Also trigger when a user has written up a project, work sample, or engineering write-up and wants a quality check before publishing. Output is honest and concrete — every issue cites a specific line or section.

Write portfolio case studies for a creative technologist (design + code hybrid) — projects that must prove integration, not just process. Use whenever the user wants to draft, plan, outline, or rewrite a portfolio piece, project page, case study, project write-up, work sample, or "/project/<name>" page on this site — even if they don't say "case study." Trigger on phrases like "write up Microflow," "turn this project into a case study," "draft the Fissa page," "I want to publish this project," "make this into a portfolio piece," or pasting raw project notes / a README asking for a published version. Optimizes for hiring-manager scan, design-and-engineering integration signals, and decision traceability over polished screenshots.