1,645 件 ・ 関連度順
概要と使いどころ
Load this skill whenever the project contains navigation components — primary navigation menus, dropdown menus, mega menus, breadcrumbs, pagination, mobile hamburger menus, or in-page jump navigation. Under no circumstances create navigation without proper landmark roles, keyboard support, and accessible labels. Absolutely always wrap navigation in <nav> with a unique aria-label.
日本語の概要は準備中です。原文の説明を表示しています。
[Investigation] Use when about to author a new Feature Spec from an idea — investigate all existing Feature Specs AND related code logic first to surface related/overlapping/affected specs, missing features, missing test cases/user stories, system unknowns, and the invariant landscape, before any spec is drafted.
日本語の概要は準備中です。原文の説明を表示しています。
[Research] Use when you need to analyze market landscape: competitors, sizing (TAM/SAM/SOM), trends, SWOT, customer segments.
日本語の概要は準備中です。原文の説明を表示しています。
[Content] Use when you need to create high-converting copy for marketing materials, social media, landing pages, email campaigns, and product descriptions.
日本語の概要は準備中です。原文の説明を表示しています。
Rewrite text that did not land, with clear context, plain language, and my writing preferences.
日本語の概要は準備中です。原文の説明を表示しています。
Stop. That last message did not land — re-pitch it.
日本語の概要は準備中です。原文の説明を表示しています。
Preview a signed-off design one release phase at a time — cut it down into a series of phase screens, each showing only what exists by that phase with the layout untouched, then put them on a scrubber you drag to watch the screen fill in release by release. Use when the user wants a Phase 1 / MVP version of an existing wireframe or mockup, phased or staged screens, a design sliced by release phase or story map, or wants to see what a screen looks like before later features land.
日本語の概要は準備中です。原文の説明を表示しています。
GStack review method for pre-landing code, diff, PR, or implementation review focused on bugs, regressions, missing tests, and release risks.
日本語の概要は準備中です。原文の説明を表示しています。
GStack ship method for final landing, PR, changelog, release, and deploy readiness checklists when the user explicitly wants to ship.
日本語の概要は準備中です。原文の説明を表示しています。
GStack design-review method for reviewing rendered UI, landing pages, decks, or visual artifacts for hierarchy, layout, accessibility, and polish.
日本語の概要は準備中です。原文の説明を表示しています。
SOP for the architect-tier campaign workflow (/campaign): exhaustive survey, mitigation planning, tiered orchestration, and reconciliation. Trigger when: - Running a multi-workstream initiative where an expensive architect-tier council surveys, plans, emits worker prompts, and judges landed work. - Conducting production-readiness assessments that fan out into autonomous mitigation dispatches across model tiers. - Prompt contains: /campaign, campaign workflow, survey, orchestrate, reconcile, premise freshness, tier routing, worker IBC, scratch.
日本語の概要は準備中です。原文の説明を表示しています。
Discipline for repairing a false claim once it has propagated: select what depends on it, produce a replacement, and accept with an expiring verdict. Trigger when: - A claim, citation, premise, or documented fact is found wrong and its downstream consequences must be traced and fixed. - A refutation, a failed re-run, a retracted external source, or a human correction lands against something already closed or already promoted. - Prompt contains: /remediation, remediation, retraction, false claim, propagated error, scrub, correction propagation, born-false, became-false, currency verdict, impeachment queue.
日本語の概要は準備中です。原文の説明を表示しています。
Day-to-day operation runbook for nuxt-crouton apps — boot any app/POC locally with auth working, seed and inspect the local database (including the miniflare-vs-.data split that makes seeded data "disappear"), turn on the review overlay / eruda, observe deployed staging (tail, smoke, row counts), and capture screenshots. Use when asked to "run the app", "boot velo/fanfare/a poc locally", "why can't I log in locally", "seed the database", "the seed data doesn't show up", "look at the local db", "check what's on staging", "screenshot the app", or "where do the artifacts land".
日本語の概要は準備中です。原文の説明を表示しています。
AID Phase 5 - QA and Release. Use for validating implementations, acceptance tests, preparing releases, deployment, operational readiness.
日本語の概要は準備中です。原文の説明を表示しています。
AID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA.
日本語の概要は準備中です。原文の説明を表示しています。
AID Phase 0 - Research & discovery. Use for validating problem spaces, identifying stakeholders, defining success metrics, deciding whether to proceed.
日本語の概要は準備中です。原文の説明を表示しています。
Data Scientist role within the AID methodology. Activate when working on: EDA, feasibility assessment, experiment planning, ML architecture, model development & validation, or production deployment & monitoring. Stack-agnostic — ask the user for their stack at the start of any new project.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive code review for commits and pull requests. Covers security, TDD, code quality, and documentation standards.
日本語の概要は準備中です。原文の説明を表示しています。
AID Phase 1 - PRD creation. Use for user stories, acceptance criteria, scoping features, transitioning from discovery to tech spec.
日本語の概要は準備中です。原文の説明を表示しています。
Real-time work context tracking for session continuity. Maintains task/step state across sessions, tracks progress, manages logs, integrates with phase enforcement.
日本語の概要は準備中です。原文の説明を表示しています。
Cucumber BDD integration for AID methodology. Gherkin-first acceptance criteria with executable specifications. Use for writing feature files, step definitions, and running acceptance tests.
日本語の概要は準備中です。原文の説明を表示しています。
Decision transparency, feedback collection, and debate invitations for AID methodology. Active in ALL phases for ALL roles.
日本語の概要は準備中です。原文の説明を表示しています。
[OPTIONAL] AI-powered visual generation using Google Nano Banana Pro. For user flows, architecture diagrams, mockups.
日本語の概要は準備中です。原文の説明を表示しています。
AID methodology phase gate enforcement. Ensures work follows correct 6-phase order (Discovery -> PRD -> Tech Spec -> Impl Plan -> Dev -> QA & Ship). Enforces gates, validates transitions. Use before any work to check the current phase and refuse work belonging to a later phase.
日本語の概要は準備中です。原文の説明を表示しています。