How do I install the Frontend Specialists skill?

Run npx skillmds@latest add majiayu000/frontend-specialists in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Frontend Specialists safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Frontend Specialists?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Frontend Specialists free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Frontend Specialists?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Frontend Specialists by majiayu000 — Agent Skill

Name: Frontend Specialists
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

STANDARD OPERATING PROCEDURE

Purpose

Plan and implement frontend features and architectures with strong accessibility, performance, and reliability practices.

Triggers

Positive: Frontend feature work, performance tuning, accessibility audits, design-to-dev translation, state management decisions.
Negative: Pure backend/system design (route elsewhere) or prompt rewrites (prompt-architect).

Guardrails

Structure-first: maintain SKILL.md, examples/, tests/, resources/, and react-specialist docs; fill gaps before work.
Constraint clarity: HARD/SOFT/INFERRED (framework, bundle budget, perf targets, accessibility requirements, release cadence).
Quality gates: lint/format, type-check, tests (unit/e2e), accessibility/perf checks.
Confidence ceiling enforced (inference/report 0.70; research 0.85; observation/definition 0.95).

Execution Phases

Intake: Capture framework (React/Next/etc.), design assets, perf/a11y targets, and release constraints.
Design: Choose state management, routing, data-fetching strategy; define component contracts and error handling.
Implementation: Build components with accessibility defaults, performance safeguards (code-splitting, memoization), and logging.
Validation: Run lint/format/type/test; measure Core Web Vitals and a11y checks; run regression snapshots where applicable.
Delivery: Provide changelog, release plan, monitoring hooks, and rollback steps.

Output Format

Request summary + constraints.
Architecture/component plan and rationale.
Validation results and risks.
Confidence with ceiling.

Validation Checklist

Constraints confirmed and design assets referenced.
Perf/a11y targets defined and measured.
Lint/format/type/test run.
Confidence ceiling stated.

VCL COMPLIANCE APPENDIX (Internal)

[[HON:teineigo]] [[MOR:root:F-R-N]] [[COM:Frontend+Usta]] [[CLS:ge_skill]] [[EVD:-DI]] [[ASP:nesov.]] [[SPC:path:/skills/specialists/frontend-specialists]]

[[HON:teineigo]] [[MOR:root:E-P-S]] [[COM:Epistemik+Tavan]] [[CLS:ge_rule]] [[EVD:-DI]] [[ASP:nesov.]] [[SPC:coord:EVD-CONF]]

Confidence: 0.71 (ceiling: inference 0.70) - SOP refreshed with prompt-architect constraint handling and skill-forge structure-first rules.

---name: frontend-specialistsdescription: Deliver resilient frontend solutions with performance, accessibility, and UX guardrails.--- ## STANDARD OPERATING PROCEDURE ### Purpose Plan and implement frontend features and architectures with strong accessibility, performance, and reliability practices. ### Triggers - **Positive:** Frontend feature work, performance tuning, accessibility audits, design-to-dev translation, state management decisions. - **Negative:** Pure backend/system design (route elsewhere) or prompt rewrites (prompt-architect). ### Guardrails - Structure-first: maintain `SKILL.md`, `examples/`, `tests/`, `resources/`, and `react-specialist` docs; fill gaps before work. - Constraint clarity: HARD/SOFT/INFERRED (framework, bundle budget, perf targets, accessibility requirements, release cadence). - Quality gates: lint/format, type-check, tests (unit/e2e), accessibility/perf checks. - Confidence ceiling enforced (inference/report 0.70; research 0.85; observation/definition 0.95). ### Execution Phases 1. **Intake**: Capture framework (React/Next/etc.), design assets, perf/a11y targets, and release constraints. 2. **Design**: Choose state management, routing, data-fetching strategy; define component contracts and error handling. 3. **Implementation**: Build components with accessibility defaults, performance safeguards (code-splitting, memoization), and logging. 4. **Validation**: Run lint/format/type/test; measure Core Web Vitals and a11y checks; run regression snapshots where applicable. 5. **Delivery**: Provide changelog, release plan, monitoring hooks, and rollback steps. ### Output Format - Request summary + constraints. - Architecture/component plan and rationale. - Validation results and risks. - Confidence with ceiling. ### Validation Checklist - [ ] Constraints confirmed and design assets referenced. - [ ] Perf/a11y targets defined and measured. - [ ] Lint/format/type/test run. - [ ] Confidence ceiling stated. ## VCL COMPLIANCE APPENDIX (Internal) [[HON:teineigo]] [[MOR:root:F-R-N]] [[COM:Frontend+Usta]] [[CLS:ge_skill]] [[EVD:-DI<gozlem>]] [[ASP:nesov.]] [[SPC:path:/skills/specialists/frontend-specialists]] [[HON:teineigo]] [[MOR:root:E-P-S]] [[COM:Epistemik+Tavan]] [[CLS:ge_rule]] [[EVD:-DI<gozlem>]] [[ASP:nesov.]] [[SPC:coord:EVD-CONF]] Confidence: 0.71 (ceiling: inference 0.70) - SOP refreshed with prompt-architect constraint handling and skill-forge structure-first rules.

Frequently asked questions

Frontend Specialists