Loading...
Loading...
Found 551 Skills
Front-end routing specification, including routing file organization structure, dynamic routing generation, static auxiliary routing writing, RouteMeta meta information fields, and routing guard logic. Suitable for projects based on vue-vben-admin v5. This skill is used when you need to add new routes, configure routing permissions, write routing guards, or modify routing-related files.
Translate PRDs into detailed UX specifications including user flows, screen descriptions, components, and interaction patterns. Use when a user has a PRD and needs to define the concrete UI/UX before generating development prompts. Bridges product requirements to implementation details.
Use when onboarding to an existing codebase that lacks specifications — exhaustively traces code paths and produces implementation-free behavioral specifications for safe refactoring, feature addition, or legacy modernization
Produce a high-level technical design with architecture diagram, component responsibilities, data flow, and test scenario map. Use after the product intent specification is approved.
Search LCSC Electronics for electronic components — find parts by LCSC number (Cxxxxx) or MPN, check stock/pricing, download datasheets, analyze specifications. Sister company to JLCPCB, same parts library. Sync and maintain a local datasheets directory for a KiCad project, or use batch MPN-list seeding (`--mpn-list`) for bulk workflows without a project. No API key needed — uses the free jlcsearch community API. Use this skill when the user mentions LCSC, JLCPCB parts library, JLCPCB assembly parts, production sourcing, Cxxxxx part numbers, needs to find LCSC equivalents for parts, is preparing a BOM for JLCPCB assembly, or wants to download datasheets and LCSC is available. For package cross-reference tables and BOM workflow, see the `bom` skill.
Execute tasks through competitive multi-agent generation, meta-judge evaluation specification, multi-judge evaluation, and evidence-based synthesis
PRD/Requirement Document Anti-Omission Assistant. When a user provides a requirement document (PRD, functional specification, product document, etc.) and requests to generate front-end pages, implement functions, or carry out development, this Skill must be used first to convert the requirement document into a structured Checklist, then implement code module by module to prevent function omissions. Trigger scenarios: The user sends a .md/.docx/.pdf requirement document and asks you to "generate pages", "implement functions", "write code", "develop this system"; the user says "develop according to this PRD", "generate based on the requirement document", "implement this document"; the user provides a requirement description of more than 200 lines. Even if the user does not mention the checklist, this process should be automatically triggered if the input is a long requirement document (>200 lines) and the goal is to generate code.
Generate clear, standardized git commit messages based on code changes (diffs), following Conventional Commits specification.
Baklib Site Theme (Template) Development: Liquid directory and naming conventions, objects and directives/filters, static page URLs, seeds and migrations; including 'Create Theme Scaffold' (themes/ directory and minimal files) and 'Reference Site Cloning Workflow' (requires confirmation gates and quality checklists). Used when users write or modify .liquid files, create new templates, clone reference sites, or troubleshoot template syntax and variables; detailed specifications can be found in references/.
End-to-end ***plain spec authoring workflow: runs a structured QA interview (product, tech stack, behavior) then produces complete .plain specification files with automated review. Use when the user wants to build something new from scratch or asks to start a new project.
Generate comprehensive OpenSpec specifications directly from the current project state. Use when the user wants to create or populate main specs by analyzing existing code, documentation, AGENTS.md, GitHub issues, and pull requests — without going through the change/proposal workflow. Ideal for bootstrapping specs on a project that already has working code but no specs yet, or for refreshing specs to match the current implementation.
Draw.io Diagram Expert: Used to generate and export `.drawio` diagrams. Activate when users request draw.io, diagrams.net, flowcharts, architecture diagrams, sequence diagrams, ER diagrams, state diagrams, mind maps, or explicitly mention `.drawio`, PNG/SVG/PDF export, or illustrations for technical articles. Defaults to a professional technical style and follows the visual specifications of floracat-architecture-diagram.