notque/vexjoy-agent / skills/frontend/frontend
frontend
UnverifiedFrontend: UI design, distinctive visual styles, HTML artifacts, Three.js 3D, TypeScript/React/Next.js apps, e-commerce, portfolios, React Native, web performance.
templates/saved/system-design.slots.json
View on GitHub{
"template": "system-design",
"shape": "report",
"description": "System design doc: overview, requirements, architecture diagram, components, data flow, tradeoffs, operational considerations.",
"slots": [
{ "name": "TITLE", "required": true, "description": "System/design name, plain text." },
{ "name": "KICKER", "required": false, "description": "Small uppercase label (e.g. 'RFC 012 · System Design')." },
{ "name": "SUBTITLE", "required": true, "description": "One-line description of what the system does." },
{ "name": "META", "required": false, "description": "Inline meta spans: author, status, date." },
{ "name": "OVERVIEW", "required": true, "description": "TL;DR overview: one or more <p> paragraphs." },
{ "name": "REQUIREMENTS", "required": true, "description": "Functional and non-functional requirements as a list or table." },
{ "name": "DIAGRAM", "required": true, "description": "Inline SVG or ASCII architecture diagram. Sits inside a .diagram box." },
{ "name": "COMPONENTS", "required": true, "description": "Components as an HTML <table>: name, responsibility, tech." },
{ "name": "DATA_FLOW", "required": true, "description": "Data flow: ordered <ol> or paragraphs describing request/event path." },
{ "name": "TRADEOFFS", "required": true, "description": "Design tradeoffs and rejected alternatives, as a table or list." },
{ "name": "OPERATIONS", "required": true, "description": "Operational considerations: scaling, failure modes, monitoring, rollback." },
{ "name": "FOOTER", "required": false, "description": "Footer: source, date, author." }
]
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |