1,645 件 ・ 関連度順
概要と使いどころ
Workflow Phase 11 — Commit Preparation and Execution. Stages and commits the work. Requires `/grant-commit` first (Git Commit Guard enforces a 15-min ad-hoc consent window; inside a workflow the grant is slug-scoped and one grant covers the whole landing).
日本語の概要は準備中です。原文の説明を表示しています。
Phase 10.6 — sync the project's execution roadmap (project.json → roadmap.path, default docs/roadmap-execution-plan.md) to the just-landed work. Flips the tasks named in workflow.json → roadmap_tasks[] from ⬜ to ✅ and promotes their epic headings ⬜→🟡→✅, preserving the standup parser format contract. On the epic track it appends instead — the epic's heading plus one row per slice — and stamps roadmap_epic back into the epic state. Also hosts the ad-hoc backfill that puts every epic already on disk onto the roadmap. Fail-open: never throws, no-ops when roadmap.path is unset/absent or no task matches, and never blocks a commit. Runs after /archive and before /memory-sync on every committing track.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see email-sequence. For popup copy, see popup-cro. For editing existing copy, see copy-editing.
日本語の概要は準備中です。原文の説明を表示しています。
Practical UI refactoring and visual design review inspired by Refactoring UI by Steve Schoger and Adam Wathan. Use when an AI coding agent needs to improve an existing interface, audit visual polish, redesign a rough UI, review frontend code for hierarchy/spacing/typography/color/depth/image issues, or turn a plain implementation into a cleaner product-quality screen. Do not use for creating UI from scratch, scaffolding a new app, building a new landing page, or designing a new design system unless the user explicitly asks to review or refactor an existing interface.
日本語の概要は準備中です。原文の説明を表示しています。
Review proposed abstractions, dependencies, and configuration for concrete consumers and maintenance cost when simplifying a design or checking overengineering.
日本語の概要は準備中です。原文の説明を表示しています。
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
日本語の概要は準備中です。原文の説明を表示しています。
Skill for building with the Astro web framework. Helps create Astro components and pages, configure SSR adapters, set up content collections, deploy static sites, and manage project structure and CLI commands. Use when the user needs to work with Astro, mentions .astro files, asks about static site generation (SSG), islands architecture, content collections, or deploying an Astro project.
日本語の概要は準備中です。原文の説明を表示しています。
Design one-off HTML artifacts (landing, deck, prototype).
日本語の概要は準備中です。原文の説明を表示しています。
Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.
日本語の概要は準備中です。原文の説明を表示しています。
Builds the "Report Sources" child page for a finished Weekly Community Signal report — an evidence-backed defense of WHY every item landed in the column/section/rank it did. The agent argues each placement like a lawyer (claim → evidence → rule → rebuttal) but is under oath: it CANNOT invent, spin, or overstate — every claim ties to a verifiable fact (issue #, label, PR type, quoted comment, npm output, the front-door test). Not CYA — it's so Nathan can defend the report with facts and see the exact reasoning behind each call. Runs after the report (invoked by weekly-report, last steps) and on "report sources", "defend the report", "why is this here".
日本語の概要は準備中です。原文の説明を表示しています。
Stop. That last message did not land — re-pitch it.
日本語の概要は準備中です。原文の説明を表示しています。
Amplify safe or boring designs to make them more visually interesting and stimulating. Increases impact while maintaining usability. Use when the user says the design looks bland, generic, too safe, lacks personality, or wants more visual impact and character.
日本語の概要は準備中です。原文の説明を表示しています。
This skill is for interface design — dashboards, admin panels, apps, tools, and interactive products. NOT for marketing design (landing pages, marketing sites, campaigns).
日本語の概要は準備中です。原文の説明を表示しています。
Opinionated constraints for building better web interfaces with coding agents. Use this skill whenever the user asks you to build, review, or fix a UI — landing pages, dashboards, components, or any frontend code — and whenever you write Tailwind CSS, motion/react animations, accessible component primitives (Base UI, React Aria, Radix), or review agent-generated interface code for quality, accessibility, and performance. Also trigger for "make the UI better", "review my interface", "clean up this component", or any frontend work in React, Next.js, or plain HTML/CSS.
日本語の概要は準備中です。原文の説明を表示しています。
Cloud guardrails for any vendor workload — Google Cloud (GCP, Vertex AI, GKE), AWS (IAM, EKS, Bedrock), Azure (Entra ID, Policy, AKS), Alibaba Cloud (RAM, mainland/international residency). Enforces identity least-privilege, mechanical policy, data boundaries, residency, cost caps, network egress and observability, with official-source validation before any claim. Trigger on any cloud infrastructure design, review, Terraform plan, or LLM/agent deployment; the-architect routes here.
日本語の概要は準備中です。原文の説明を表示しています。
Crie designs de websites premium com qualidade Awwwards como componentes React (.jsx) que pareçam ter sido construídos por uma agência de primeira linha cobrando R$250k+ por projeto. Use esta skill sempre que o usuário pedir um website, landing page, portfólio, ou componente web que deve parecer caro, premium, luxo, editorial, high-end, ou de qualidade agência. Também dispare quando o usuário mencionar Awwwards, FWA, design premiado, ou referenciar marcas como Apple, Aesop, Bottega Veneta, Stripe, ou qualquer marca luxury/fashion/design-forward. Dispare quando o usuário disser coisas como "faça parecer profissional", "faça parecer caro", "quero que fique realmente bom", "design de alta qualidade", "não genérico", ou expressar insatisfação com aesthetics típicos de websites gerados por IA. NÃO dispare para dashboards, admin panels, ferramentas internas, ou UI funcional onde aesthetics são secundárias à utilidade — a skill padrão frontend-design cuida disso.
日本語の概要は準備中です。原文の説明を表示しています。
Inteligência de design UI/UX. 50 estilos, 21 paletas, 50 combinações de fontes, 20 gráficos, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Ações: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projetos: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elementos: button, modal, navbar, sidebar, card, table, form, chart. Estilos: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Tópicos: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrações: shadcn/ui MCP para busca de componentes e exemplos.
日本語の概要は準備中です。原文の説明を表示しています。
Criar interfaces frontend distintas e de qualidade produtiva com alto padrão de design. Use essa habilidade quando o usuário pedir para construir componentes web, páginas, artefatos, pôsteres ou aplicações (exemplos incluem websites, landing pages, dashboards, componentes React, layouts HTML/CSS, ou ao estilizar/embelezar qualquer UI web). Gera código criativo e polido com UI design que evita estéticas genéricas de IA.
日本語の概要は準備中です。原文の説明を表示しています。
Quando o usuário quer otimizar, melhorar ou aumentar conversões em qualquer página de marketing — incluindo homepage, landing pages, páginas de preços, páginas de features ou posts de blog. Também use quando o usuário menciona "CRO," "otimização de taxa de conversão," "essa página não está convertendo," "melhorar conversões," ou "por que essa página não funciona." Para fluxos de signup/registro, veja signup-flow-cro. Para ativação pós-signup, veja onboarding-cro. Para formulários fora de signup, veja form-cro. Para popups/modals, veja popup-cro.
日本語の概要は準備中です。原文の説明を表示しています。
Quando o usuário quer escrever, reescrever ou melhorar copy de marketing para qualquer página — incluindo homepage, landing pages, páginas de preço, páginas de funcionalidade, páginas "sobre" ou páginas de produto. Também use quando o usuário disser "escreva copy para", "melhore essa copy", "reescreva essa página", "copy de marketing", "ajuda com headline" ou "copy de CTA". Para copy de email, veja email-sequence. Para copy de popup, veja popup-cro.
日本語の概要は準備中です。原文の説明を表示しています。
Agentes de voz representam a fronteira da interação com IA - humanos falando naturalmente com sistemas de IA. O desafio não é apenas reconhecimento e síntese de fala, mas alcançar fluxo de conversa natural com latência inferior a 800ms enquanto se lidam com interrupções, ruído de fundo e nuances emocionais. Esta habilidade cobre duas arquiteturas: fala-para-fala (OpenAI Realtime API, menor latência, mais natural) e pipeline (STT→LLM→TTS, mais controle, mais fácil de depurar). Insight-chave: latência é a restrição. Hu
日本語の概要は準備中です。原文の説明を表示しています。
Quando o usuário quer criar páginas de comparação com concorrentes ou alternativas para SEO e ativação de vendas. Use também quando o usuário menciona 'página de alternativas', 'página vs', 'comparação com concorrentes', 'página de comparação', '[Produto] vs [Produto]', '[Produto] alternativa', ou 'landing pages competitivas'. Cobre quatro formatos: alternativa singular, alternativas plurais, você vs concorrente, e concorrente vs concorrente. Enfatiza pesquisa profunda, arquitetura de conteúdo modular e tipos de seção variados além de tabelas de recursos.
日本語の概要は準備中です。原文の説明を表示しています。
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
日本語の概要は準備中です。原文の説明を表示しています。
Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.
日本語の概要は準備中です。原文の説明を表示しています。