Loading...
Loading...
Found 2,894 Skills
Guide for creating effective skills for Apollo Solutions and Field teams. Use this skill when: (1) users want to create a new skill for this repository, (2) users want to update an existing skill, (3) users ask about skill structure or best practices, (4) users need help writing SKILL.md files.
Analyze the current project structure, package manager, and build tools to generate a comprehensive, standardized CONTRIBUTING.md file. Trigger when the user asks to write or generate a contributing guide, or wants to know how to set up the project locally for development.
Initialize a new project with deep context gathering and PROJECT.md
Use this skill when users ask for frontend library/framework usage, APIs, best practices, or examples (e.g. Vue, Vite, React, Tailwind). Always fetch up-to-date docs with Context7.
Provides rules for writing effective skill descriptions. Use this when setting up frontmatter properties for agent skill documents using starlight-skills. Do not use this for structuring the actual text body or plugin configuration options.
Use this skill whenever creating or editing any markdown file. Do not wait for an explicit request — if a markdown file is being created or edited, this skill applies.
API reference: UIKit. Query for UIView, UIViewController, controls, table and collection views, navigation controllers, scenes, Auto Layout, images, colors, gestures, presentation, and SwiftUI hosting.
Deep single-word English mastery skill. Unpacks one English word's semantic image, modern usage, confusion points, and memory hook. Use when the user wants to deeply understand one English word, asks for deeper meaning or usage rather than translation, or wants a memorable vocabulary breakdown. Prefer this over `plain` or `learn` for a single vocabulary item. Do not use it for phrases, sentence translation, or multiple words at once; route multi-word card workflows to `word-flow`.
Gather phase context through adaptive questioning before planning
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
Regenerate docs/INDEX.md using docs/prompts/PROMPT-INDEX.md with a preflight plan, direct execution, validation, and post-action review (explicit-only).
Conversationally guides the user to a CLAUDE.md file. Starts by inferring what it can from the repo, asks ~8 core questions, then offers optional depth across business, voice, and working-style topics. Use when the user wants a CLAUDE.md but would rather have a conversation than fill out a form.