frontend-design-principles
Frontend Design Principles
Build frontend interfaces with craft and intention.
Scope & Routing
After reading this file, load additional guidance based on what you're building:
Load app.md when building:
- Dashboards and admin interfaces
- Settings panels and configuration screens
- Internal tools and SaaS products
- Data-heavy interfaces with tables, forms, lists
- Any interface where users work repeatedly
Load marketing.md when building:
- Landing pages and marketing sites
- Promotional materials and announcements
- Creative artifacts and posters
More from joshuadavidthomas/agent-skills
writing-clearly-and-concisely
Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.
13crafting-effective-readmes
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
12reducing-entropy
Use when evaluating designs, reviewing code, or refactoring - measures success by total code in the final codebase, not effort to get there. Bias toward deletion.
10improving-prompts
Use when optimizing CLAUDE.md, AGENTS.md, custom commands, or skill files for Claude 4.5 models - applies documented Anthropic best practices systematically instead of inventing improvements
10diataxis
Structure, classify, and write documentation using the Diátaxis framework. Use when writing docs, README files, guides, tutorials, how-to guides, API references, or organizing documentation architecture. Also use when asked to improve documentation, restructure docs, decide what type of doc to write, or classify existing content. Covers tutorials, how-to guides, reference, and explanation.
8sveltekit
>
6