Design case-study portfolio

Show the problem, work, and outcomes behind selected projects.

Customize the recipe

0/1500 characters
Workflow boosters

Prompt preview

# Design case-study portfolio

Show the problem, work, and outcomes behind selected projects.

## Deliverable
A portfolio index and reusable, deep-linkable case study layout.

## Stack and visual direction
- Recommended starting stack: Next.js, TypeScript and semantic CSS. Use static content where it serves the brief.
- Editorial: Use strong display typography, readable measure and deliberate placement of images and captions. Let the content determine the grid and pacing. Apply this direction to the website.

- Inspect the workspace first. Adapt to its stack when it contains a project, or use the recommended starting stack in a new workspace.

## Tools and setup · Universal
Use the receiving agent’s documented skill and tool mechanisms. Match setup to the agent and workspace you actually have.

Check available tools first. Propose documented project-level setup only when it materially helps and follow the host's permission prompts. If a tool or integration is unavailable, continue with the workflow below using existing tools, local fixtures or a manual check. Keep secrets in the intended configuration environment.

- [Frontend Design](https://github.com/anthropics/skills/tree/main/skills/frontend-design) (Skill) — Plan distinct typography, composition and interaction details before building UI.
  Fallback: Write a short plan for hierarchy, palette, spacing and interaction states, then review the actual screens against it.
- [Next.js](https://github.com/vercel/next.js) (Repository) — Use App Router conventions, server rendering, metadata and accessible route structure.
  [Official setup](https://nextjs.org/docs/app/getting-started/installation).
- [Sharp](https://github.com/lovell/sharp) (Repository) — Generate appropriately sized derivatives and preserve originals during asset optimization.

## Workflow
1. Structure each case as challenge, constraints, decisions, iteration, and evidence. Pair captions with optimized images and cite provided outcome data.
2. Use the simplest implementation that delivers the stated outcome. Follow the user's project constraints and treat the starting stack as a default. Reuse existing work and ask for essential input only when it would change the result. Use realistic labeled sample data when real inputs are unavailable.
3. Run the applicable checks and report what actually passed along with any checks you could not run.

## Acceptance checks
- [ ] Readers can jump to and navigate sections with keyboard controls.
- [ ] Image derivatives remain sharp at their display widths and have useful alternatives.
- [ ] Walk the primary journey with keyboard only. Check visible focus, logical order, accessible names, readable contrast, zoom and reduced motion. Use axe where available and manually check behavior that automation cannot assess.
- [ ] Check mobile navigation and every key page at narrow and desktop widths. Remove horizontal document overflow and optimize images with stable dimensions and appropriate alternatives.
- [ ] Check working buttons, links and footer destinations, clickable logo and contact paths where applicable, page titles, descriptions, favicon, a useful 404 and the current copyright year. Remove placeholder text and unused navigation.
- [ ] Verify forms with both valid and invalid submissions and useful success and error feedback.

Recipe resources

Source, setup, and compatibility details.