Loading...
Loading...
Found 874 Skills
Turn a material or product list into CSI MasterFormat outline specifications with three-part sections and review flags. Use to write specs; use epd-to-spec for embodied-carbon requirements.
Implement and improve the integration of Next.js and microCMS based on official information. Used for SDK setup, App Router data fetching and dynamic routes, cache/ISR/Webhook, Draft Mode, next/image implementation, and troubleshooting. For framework-independent API specifications and content design only, prioritize microcms-guide.
Implement the code changes described in a specification.
An Agent Skill that rewrites unnatural Japanese generated by AI into natural, information-dense prose that is easy for humans to read. Use it for requests such as “Make this text easier to read,” “Remove the AI-like tone,” “Get rid of the AI smell,” “Make this sound like natural Japanese,” or “De-AI-ify this text,” and when editing technical articles, business specifications, PR descriptions, essays, and note posts. It breaks down inanimate subjects, makes figurative verbs concrete, completely removes emojis and end-of-sentence colons, deletes unnecessary parenthetical asides, removes awkward half-width spaces around English words, converts excessive boldface, bullet lists, and negative contrast into plain prose, and reconstructs each sentence so that it clearly conveys who did what to whom and how.
Hub skill for requirements elicitation. Provides technique selection, orchestration guidance, LLMREI patterns, and autonomy level configuration. Use when gathering requirements from stakeholders, conducting elicitation sessions, or preparing requirements for specification.
Conduct structured interviews to gather requirements, clarify specifications, or understand context. This skill should be used when starting a new task that requires understanding user intent, requirements, technical specifications, or context. It supports various interview types including requirements definition, debugging investigation, architecture review, and general information gathering.
Portable AI identity system using AIEOS (AI Entity Object Specification) - import, export, and manage agent personas in a standardized JSON format.
Creates a concise one-page solution overview that communicates the proposed approach, key decisions, and trade-offs. Use when pitching solutions to stakeholders, aligning teams on approach, or documenting solution intent before detailed specification.
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.
Validate DESIGN.md files against the official Google specification using the `@google/design.md` CLI linter. Works with local files. Use when the user wants to lint a DESIGN.md, check spec compliance, find broken token references, verify WCAG contrast ratios, diff two versions, export tokens to Tailwind or DTCG format, or audit a design system file for structural correctness. Trigger on mentions of "validate DESIGN.md", "lint DESIGN.md", "check my design.md", "design.md spec compliance", "WCAG contrast check", "broken token references", "design token validation", "export design tokens", "diff design systems", "design.md audit", "@google/design.md", "npx design.md lint", "design system validation", "frontmatter tokens", or any request to verify a DESIGN.md file.
Use when designing futuristic agentic workflows, when wanting AI to proactively act on team communications, or when eliminating the bottleneck of formal specifications
Token architecture, component specifications, and slide generation. Three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, component specs, strategic slide creation. Use for design tokens, systematic design, brand-compliant presentations.