frontend-architect
Skillset for frontend design and implementation. Use when working on UI, components, accessibility, or client-side code; load referenced skills when their context matches the task.
Works with
--- name: frontend-architect description: Skillset for frontend design and implementation. Use when working on UI, components, accessibility, or client-side code; load referenced skills when their context matches the task. license: MIT --- # Frontend Skillset Single entry point for **frontend** work: UI components, accessibility, performance, and client-side implementation. Apply the skills below when their context matches the task. Read each skill from `.cursor/skills/<skill>/SKILL.md` when needed. ## Skills in this set | Skill | Path | When to use | |-------|------|-------------| | `accessibility-checklist` | `.cursor/skills/accessibility-checklist/SKILL.md` | Building or reviewing UI—WCAG 2.1 AA, keyboard, screen readers, semantics | | `performance-profiling` | `.cursor/skills/performance-profiling/SKILL.md` | Optimizing frontend—measure first (Core Web Vitals, bundle, load), then optimize | | `refactoring-checklist` | `.cursor/skills/refactoring-checklist/SKILL.md` | Refactoring components or UI—safe steps, behavior preservation | | `e2e-playwright` | `.cursor/skills/e2e-playwright/SKILL.md` | Components or flows that need E2E—stable selectors, POM, waits | | `code-review` | `.cursor/skills/code-review/SKILL.md` | Reviewing frontend code or PRs—correctness, a11y, performance, style | ## How to use When working on frontend tasks: 1. Read this file (`.cursor/skills/frontend-architect/SKILL.md`) first. 2. For the current task, determine which skills in the table apply. 3. Read those skill files from `.cursor/skills/<skill>/SKILL.md` and apply their guidance. ## Alignment - Follow project rules: `core-standards.mdc`, `react.mdc` / `typescript.mdc` when in scope. - Handoff: implementation notes, tests where required, and linkage to acceptance criteria per `compounding-dev-cycle.mdc`.
More Performance skills
seo-audit
coreyhaines31/marketingskills
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.
competitor-profiling
coreyhaines31/marketingskills
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
prospecting
coreyhaines31/marketingskills
When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect research," "qualified leads," "find my first customers," "early adopters," "design partners," "beta users," or "who has this problem." Use this for the list-building and qualification phase. For writing the outbound copy after the list is built, see cold-email. For deep competitive research on specific accounts, see competitor-profiling.
