3,639 件 ・ 関連度順
概要と使いどころ
Use when navigating kernel source, understanding boot flow, initcall levels, or major subsystems (VFS, scheduler, MM) in linux.git. Not for driver-model depth: use device-drivers.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants adversarial stress-testing of a proposed architecture, structure, or shape. Not for tasks that require source or remote-system changes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when non-trivial code needs a design, codebase design or architecture needs improving, or one module needs targeted interface narrowing, seams, or testability. Not for diagrams, deploy, or irreversible changes.
日本語の概要は準備中です。原文の説明を表示しています。
Load the essential AI Factory project context before work begins. Reads configured DESCRIPTION, ARCHITECTURE, ROADMAP, RESEARCH, RULES, and applicable AGENTS.md files, then returns a compact session handoff suitable for continuing or forking. Use at the start of a new session or after context loss.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze codebases using a graph database instead of reading source files. Use when understanding code architecture, finding functions or call patterns, tracing data flow, checking dependencies, or answering "where is X used?" questions. Grafema builds a queryable code graph from static analysis — prefer querying the graph over reading files manually.
日本語の概要は準備中です。原文の説明を表示しています。
Create polished, code-driven Remotion motion explainers from scripts, narration, subtitles, product specifications, reference videos, UI recordings, diagrams, or abstract concepts. Use for product launches, AI demonstrations, UI interactions, algorithms, scientific principles, electrical systems, data flows, architecture, charts, equations, and concepts best expressed with React, SVG, Canvas, WebGL, or Three.js. Prioritize continuous spatial logic, visible cause and effect, precise interaction states, editable parameters, deterministic rendering, and evidence-backed visual QA.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks for a code review by a fleet of specialized reviewer agents, wants multiple independent reviewer perspectives, or asks to run reviewers in single-pass or iterative fix-until-clean mode. Launches focused subagents for correctness, security, architecture, conventions, simplicity, UX, reliability, telemetry, testing, compatibility, and documentation review.
日本語の概要は準備中です。原文の説明を表示しています。
Stress-test a design decision with premortem/backcast analysis, then produce a risk-calibrated recommendation that maps to ADR fields. Use when: (1) Multiple competing architecture options, (2) Irreversible or high-risk design choices, (3) /discuss identifies a complex trade-off
日本語の概要は準備中です。原文の説明を表示しています。
Write effective Architecture Decision Records. Use when: (1) Creating a new ADR, (2) Recording a design decision, (3) User mentions ADR, decision, trade-off, or alternatives
日本語の概要は準備中です。原文の説明を表示しています。
Post-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when asked to "update the docs", "sync documentation", or "post-ship docs".
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "animate this diagram", "build a flowchart that reveals step by step", "animate an architecture/sequence diagram", "make a chart animate in", "grow the bars / draw the line / count up the number", "show data flowing along a connector", or "turn a static diagram into a guided reveal". Covers SVG, Framer Motion, D3, and Remotion.
日本語の概要は準備中です。原文の説明を表示しています。
Create or redesign product UI in an existing codebase, including a wireframe, substantive visual variations, and an interactive prototype. Use for requests about UI layout, visual direction, screens, flows, components, a landing page, dashboard, or making an interface feel polished. Do not use for backend work, system architecture, decks, or logic-only UI fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Extract, document, or normalize a product UI design system from code, screenshots, or brand sources. Use for visual tokens, theme variables, typography, spacing, colors, radii, shadows, component inventories, variants, states, or building a reusable UI library. Do not use for software architecture, database schemas, or generic system design.
日本語の概要は準備中です。原文の説明を表示しています。
What LaRuche is: architecture, butinage, memory, LaReine, and its full wiki.
日本語の概要は準備中です。原文の説明を表示しています。
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
日本語の概要は準備中です。原文の説明を表示しています。
Turn travel photos with recognizable architecture or human-made landmarks into 3:4 folk ink-and-color posters, with either a photo comparison layout or a full-canvas redraw. Do not use when no landmark is recognizable.
日本語の概要は準備中です。原文の説明を表示しています。
OpenTSC v2.1: Soul/Shell architecture for interpersonal intelligence. Local, offline-first, with event graphs, judgment engine (K7), self-creation (K8), three-layer attributes, calibrated predictions, 11 VSM professions, and a pluggable zvec memory index (semantic search, identity resolution, jieba segmentation, emotion scoring incl. batched+cached LLM) that runs with zero extra deps. Transforms implicit social judgment into explicit, queryable, auditable, evolving intelligence.
日本語の概要は準備中です。原文の説明を表示しています。
Build, review, and browser-test interactive website page or module HTML from a confirmed UI Architecture Map and visual direction. Use for HTML First Drafts, restrained motion implementation, full-page or module-first prototypes, rendered design review, responsive and interaction QA, page composition, and implementation handoff. Do not use for design exploration, unconfirmed visual or motion direction, content strategy, Design Systems, Elementor controls, CMS templates, or framework components.
日本語の概要は準備中です。原文の説明を表示しています。
Design and visually validate implementation-agnostic website pages or modules from an approved Design System and confirmed content. Use for Module Design Solutions, Page UI Architecture Maps, media, evidence, page motion budgets, section motion intent, visual-direction images, and direction review before HTML. Do not use to write or review HTML/CSS/JS, run browser implementation QA, plan platform fields, or implement CMS components.
日本語の概要は準備中です。原文の説明を表示しています。
Research 3–5 confirmed same-industry or cross-industry websites and translate their brand narrative, page architecture, art direction, and visual-system evidence into one reusable Visual Reference Brief. Use when strong references are scarce, a site needs brand-led or premium positioning, a page lacks a narrative spine, or a key module lacks a credible design precedent. Do not create page content, a Design System, UI directions, HTML, or a permanent brand gallery.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a NowStack Mobile app idea into a build-ready plan. Orchestrates PRD, architecture, and tasks; optionally applies the site-config brief and hands off to implementation. Use for `ns create-app`, "create app", "plan a new app", "I have an app idea", or starting a product from scratch.
日本語の概要は準備中です。原文の説明を表示しています。
Create a lean, mobile-aware Product Requirements Document for a NowStack Mobile app through interactive discovery, then save it to .agents/plan/PRD.md. Use for "write a PRD", "ns prd", "define the product", "plan my app", or as the first planning step before ns-architecture and ns-tasks. Mobile-flavored — personas, onboarding/paywall flow, platforms (iOS/Android/web), IAP vs subscription monetization, store scope. Feeds ns-init-project (site-config) and the rest of the planning pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
Add or update NowStack Mobile docs in docs/. Use when documenting architecture, release workflows, Convex/web/mobile patterns, setup, APIs, or tooling — or via `/ns docs`.
日本語の概要は準備中です。原文の説明を表示しています。
Turn an electronic product idea, behavior description, reverse-engineering note, or incomplete circuit concept into a decision-ready engineering brief and architecture. Use before schematic design or audit when functions, operating states, power, interfaces, mechanics, production quantity, cost, or measurable requirements are missing or ambiguous.
日本語の概要は準備中です。原文の説明を表示しています。