Loading...
Loading...
Found 888 Skills
Create an icon system specification covering grid, sizing, naming, categories, and implementation guidance.
Manages persistent Knowledge Graph for specifications. Caches agent discoveries and codebase analysis to remember findings across sessions. Validates task dependencies, stores patterns, components, and APIs to avoid redundant exploration. Use when: you need to cache analysis results, remember findings, reuse previous discoveries, look up what we found, spec-to-tasks needs to persist codebase analysis, task-implementation needs to validate contracts, or any command needs to query existing patterns/components/APIs.
Guide spec-driven feature development using a structured three-phase workflow: Requirements → Design → Tasks. Use this skill whenever the user wants to plan a feature, write a spec, or do structured design before coding. Trigger on phrases like "let's spec this out", "write a specification" or "help me think through this feature".
Ascend C Code Inspection Skill. Conduct security specification inspection on code based on the hypothesis testing methodology. When calling, you must clearly provide: code snippets and inspection rule descriptions. TRIGGER when: Users request code inspection, code review, ask code security questions, check coding specifications, or need to check specific code issues (such as memory leaks, integer overflows, null pointers, etc.). Keywords: Ascend C, code inspection, code review, security specification, memory, pointer, overflow, leak, coding specification.
Document Architecture Specification (L0-L4 + common layers) and omo rule generation. Generate rules under .omo/rules/docs/ for specific projects to optimize project documentation; this skill only operates/modifies files under .omo/rules/docs/, and only generates rules without creating documentation. Two file modes: Files without the .template suffix (such as CONSTITUTION) are global Rules themselves (frontmatter copied from omo + full file content, alwaysApply globally injected); Files with the .template suffix are templates, and the generated rule = frontmatter (copied from omo fields) + four sections of main content (inline translation of generation: Trigger Conditions/Execution Process/Hard Requirements/Completion Criteria) + the "Template" section (template Markdown content, excluding YAML frontmatter). It is only triggered when the user manually requests to update the documentation specification (generate/update rules under .omo/rules/docs/), and does not trigger automatically.
Writing, registering and debugging MaaFramework Custom recognition/action — including criteria for when to adopt Custom, host and registration paths, binding implementation and registration, parameter parsing and validation, reusing pipeline nodes, Agent child process mode, and engineering specifications. Use when implementing MaaFW custom recognition or action logic, deciding registration path for your host, registering customs, parsing custom_action_param/custom_recognition_param, reusing pipeline nodes inside custom code, or setting up the agent child process mode.
Create conventional commit messages following best conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits specification.
Cinematic UI Design Guidelines. For high-expression applications such as personal brands, creative galleries, and premium players. Mandatory use of Framer Motion, Tailwind CSS, and React. Use cases: (1) Building projects requiring a "high-end feel", "cinematic feel", or "immersive feel", (2) Auditing UI code for compliance with Kinetic Minimalism specifications, (3) When users request effects similar to Apple Music, Linear, or high-end portfolios.
Manage RFC-style specifications with validation, and dynamic generation of history, index, and namings files. Use when validating RFC documents, checking taxonomy compliance, or generating specification indices and terminology references.
Advanced motion designer with decades of After Effects and motion graphics experience, specialized in creating engaging video specifications for Remotion. Use when creating video specs, planning motion graphics, designing animations, or when asked to "create a video", "design motion graphics", "plan video content", or "spec out a video". Produces detailed scene-by-scene specifications with timing, audio, sound effects, and animation descriptions.
Use GitHub Spec Kit's /speckit.implement and /speckit.tasks to systematically build missing features from specifications. Leverages implementation plans in specs/, validates against acceptance criteria, and achieves 100% spec completion. This is Step 6 of 6 in the reverse engineering process.
Test-Driven Development workflow specialist using RED-GREEN-REFACTOR cycle for test-first software development. Use when developing new features from scratch, creating isolated modules, or when behavior specification drives implementation. Do NOT use for refactoring existing code (use moai-workflow-ddd instead) or when behavior preservation is the primary goal.