portfolio-design
Single entry point for product design and user-facing implementation in the portfolio-website project. Use whenever work changes what a user sees, understands, chooses, or does: shaping requirements and flows; building or redesigning pages and components; reviewing URLs, screenshots, diffs, or agent findings; improving product copy, information architecture, component choice, hierarchy, layout, interaction, accessibility, responsive behavior, and loading, empty, error, or destructive states. Trigger on design, UX, UI, usability, flow, build, improve, fix, audit, review, polish, simplify, or production-ready requests. Also use when backend behavior changes a user-visible outcome. Not for backend-only work with no user-visible effect, tests with no shipped UI impact, telemetry-only work, or documentation.
Pinned to revision 17a313a91665, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/portfolio-design/SKILL.md
- skills/portfolio-design/AGENTS.md
- skills/portfolio-design/decisions/README.md
- skills/portfolio-design/exemplars/pr-stylex-migration.md
- skills/portfolio-design/references/copy.md
- skills/portfolio-design/references/coverage-gaps.md
- skills/portfolio-design/references/glossary.md
- skills/portfolio-design/references/interface-quality.md
- skills/portfolio-design/references/patterns.md
- skills/portfolio-design/references/product-judgment.md
- skills/portfolio-design/references/resilience.md
- skills/portfolio-design/references/rules.md
- skills/portfolio-design/references/surfaces.md
Every link opens the file at its source, pinned to the revision this page describes.