Loading...
Loading...
Found 1,567 Skills
[Testing] Use when creating or enhancing unit tests, integration tests, or defining test strategies for backend and frontend code.
Meta-skill for extracting and creating reusable Claude Code skills from past work sessions. Analyzes git history, code patterns, workflows, and documentation to identify harvestable skills, then generates comprehensive skill definitions with best practices, examples, and structured templates.
When the user wants to plan content marketing across channels, define content types and formats, or create a content repurposing strategy. Also use when the user mentions "content marketing strategy," "content types," "content formats," "content repurposing," "content calendar," "content mix," "owned content," "content distribution," "content funnel," or "content planning across channels."
Proxy2.0 API 接口设计规范：RESTful URL 约定、Controller 模板、VO 设计、Swagger 文档注解、 错误码设计、响应格式。Use when: (1) Creating new Controller/API endpoints, (2) Designing VO classes (PageReqVO/SaveReqVO/RespVO), (3) Writing Swagger annotations, (4) Defining error codes, (5) Reviewing API design compliance.
Define an illustration style guide with visual language, color usage, and application rules.
Write structured strategic documents for small and medium businesses. Produces SWOT analyses, lean business plans, OKRs, and competitive analyses. Each mode has a defined structure and quality bar. Use when a business needs to articulate strategy, set goals, analyse competition, or plan for growth. Outputs actionable documents, not generic frameworks.
OmniStudio FlexCard creation and validation with 130-point scoring. Use when building at-a-glance UI cards, configuring data source bindings to Integration Procedures, or reviewing existing FlexCard definitions for accessibility and performance. TRIGGER when: user creates FlexCards, configures data sources, designs card layouts, or asks about OmniUiCard metadata. DO NOT TRIGGER when: building OmniScripts (use sf-omniscript), creating Integration Procedures (use sf-integration-procedure), or analyzing dependencies (use sf-omnistudio-analyze).
Write compelling award submissions, grant applications, and competition entries. Maps achievements to selection criteria using evidence-based narratives. Handles business awards (Telstra, chamber of commerce), industry awards, and grant applications. Use when preparing any competitive submission where you need to demonstrate merit against defined criteria.
Teaches AI to design landing pages that feel like $150k agency work. Defines exact fonts, spacing, shadows, card structures, animations, and Korean typography standards that make Supanova-generated pages feel expensive and intentional. Blocks all common defaults that make AI designs look cheap or generic.
Scope and assess new feature ideas → living doc with go/no-go. Elaborates vague ideas into clear concepts. First pipeline step. Triggers: user wants to add/build/implement any new capability. Not for: bugs (triage-issue), requirements (define), design (design/architect).
Reference library of 35+ hook and headline tactic types. Use this when a user asks for hooks organized by tactic, wants to know which tactic to use for a given situation, or requests hooks "by tactic type." This defines what each tactic is and when to deploy it. Always pair with hook-writing for execution — tactics define the frame, psychological triggers are the mechanism inside the frame.
Validate multi-skill workflows defined in CLAUDE.md by checking skill existence, inter-skill data contracts (JSON schema compatibility), file naming conventions, and handoff integrity. Use when adding new workflows, modifying skill outputs, or verifying pipeline health before release.