Frontend projects require coordinated setup, components, data flow, testing, and optimization. This skill provides practical workflows and templates for completing that work.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "frontend-developer" from https://skillstore.io/skills/zl2023github-frontend-developer.md and its manifest at https://skillstore.io/api/skills/zl2023github-frontend-developer/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.
Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Most static alerts mistake Markdown fences, inline identifiers, and TypeScript template literals for shell execution. The network, path, and environment examples are normal frontend patterns. One semantic issue remains: the authentication examples persist bearer tokens in browser storage, where injected scripts could read them.
The examples read a bearer token from localStorage and persist the authentication token through Zustand. A successful XSS attack could extract the token.
The code directly reads localStorage for an Authorization header and configures Zustand persistence for the token. Browser scripts can access this storage.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Create a typed frontend foundation, responsive pages, state management, API integration, and tests from an approved product specification.
Expand a Component Library
Implement reusable components with documented properties, interaction states, responsive behavior, accessibility support, and focused tests.
Complete Full-Stack Features
Connect existing backend endpoints to frontend views with typed models, loading states, error handling, caching, and validation.
Try These Prompts
Create a Responsive Component
Create a responsive [component] in [framework]. Define typed properties and include loading, empty, error, disabled, and mobile states.
Integrate an API
Connect [page or component] to [API endpoint]. Add typed request models, caching, loading feedback, error handling, and focused tests.
Diagnose a Frontend Defect
Investigate [bug and reproduction steps] in this repository. Identify the root cause, implement a focused fix, and add regression coverage.
Deliver a Production Feature
Implement [feature] using the existing architecture. Verify responsiveness, accessibility, security, performance, type safety, tests, linting, and the production build.
Best Practices
Provide the repository structure, framework versions, design constraints, and acceptance criteria before implementation.
Review proposed dependencies and commands before execution, especially packages fetched from external registries.
Require tests, linting, type checks, and a production build before accepting changes.
Avoid
Do not request broad rewrites when a focused component or configuration change solves the problem.
Do not expose credentials in frontend variables, browser storage, source code, or generated examples.
Do not accept visual implementation without responsive, accessibility, loading, empty, and error-state checks.
Frequently Asked Questions
Which frontend frameworks does this skill cover?
It covers React, Vue, Angular, Next.js, Nuxt, and common TypeScript tooling.
Can it start a new frontend project?
Yes. It provides workflows for scaffolding, dependencies, TypeScript, linting, formatting, routing, state management, and build verification.
Can it work in an existing repository?
Yes. Provide the repository, relevant files, framework versions, constraints, and acceptance criteria.
Does it include testing support?
Yes. It covers unit, component, and end-to-end tests with common JavaScript testing tools.
Will it execute package installation commands?
It may propose or run project commands when tools permit. Review external packages and command effects before approval.
Does it guarantee secure authentication?
No. Authentication storage, cookies, CSRF defenses, XSS defenses, and backend controls require a project-specific security review.