4,207 件 ・ 関連度順
概要と使いどころ
This skill should be used when the user asks to "generate tasks", "create implementation plan", "break down feature", "write agent prompts", "decompose into tasks", "create work items", or when creating agent-ready task descriptions from PRD and SDD documents.
日本語の概要は準備中です。原文の説明を表示しています。
North star guidance for the agent-resources project. Use this skill to understand project context, get inspiration for development decisions, and resolve uncertainty about feature priorities or design choices. Reference when asking 'why does this project exist?' or 'what should we optimize for?'
日本語の概要は準備中です。原文の説明を表示しています。
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Build applications where agents are first-class citizens. Use this skill when designing autonomous agents, creating MCP tools, implementing self-modifying systems, or building apps where features are outcomes achieved by agents operating in a loop.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when building AI agents using prompt-native architecture where features are defined in prompts, not code. Use it when creating autonomous agents, designing MCP servers, implementing self-modifying systems, or adopting the "trust the agent's intelligence" philosophy.
日本語の概要は準備中です。原文の説明を表示しています。
Manage git commits for autonomous coding. Use when committing feature implementations, creating descriptive commits, managing git workflow, or handling version control.
日本語の概要は準備中です。原文の説明を表示しています。
a set of guidelines to build with Botpress's Agent Development Kit (ADK) - use these whenever you're tasked with building a feature using the ADK
日本語の概要は準備中です。原文の説明を表示しています。
Pull latest origin/main into the current local branch and resolve merge conflicts (aka update-branch). Use when Codex needs to sync a feature branch with origin, perform a merge-based update (not rebase), and guide conflict resolution best practices.
日本語の概要は準備中です。原文の説明を表示しています。
30 → 5 → 15 funnel for brainstorming new features on the existing Forge codebase. Use when adding capability to a mature install, not for greenfield.
日本語の概要は準備中です。原文の説明を表示しています。
Start a new Flywheel planning round. Produce initial markdown plan, route to competing frontier models, synthesize hybrid, refine 4–5×. Use before any coding begins on a new feature.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a rough feature, product interaction, or architecture idea into a concrete design. Use when meaningful decisions remain open; avoid for already-clear local edits.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a feature into well-defined, independently shippable slices — whether it's an epic that needs breaking apart or a single story that needs sharpening into a job story
日本語の概要は準備中です。原文の説明を表示しています。
Turn the working changes into one or more atomic commits with well-written messages. Use whenever the user runs /git-commit or asks to commit their work, wrap up a feature, or "commit what I have."
日本語の概要は準備中です。原文の説明を表示しています。
Super Base Context — project doc loader & synchronizer. Triggers even without explicit "load docs"/"sync docs." READ MODE — load architecture/modules/coding/decision docs when work references project state: code work (write/modify/remove); design (features/APIs/schemas/architecture); review (modules, past solutions); tech selection; ADR research; migration/refactor planning; performance/security analysis; tests; code reviews; any spec/plan/design/ADR referencing project. WRITE MODE — NET DELTA vs. last doc sync: additions/modifications/REMOVALS/deprecations of previously-synced code or decisions (docs revert: delete BCU file/ADR), AND rollbacks. User signals: sync docs/done/ready to commit/pre-commit/record decision. Auto-fires before final task-completion reply. WRITE MODE does NOT fire on: brainstorming, generic/read-only Q&A, in-session try-and-undo with no net change, already-synced.
日本語の概要は準備中です。原文の説明を表示しています。
Generate missing documentation from scratch for a feature, module, or entire project. (gstack).
日本語の概要は準備中です。原文の説明を表示しています。
"Apply spiral of silence theory (Noelle-Neumann) to analyze how perceived opinion climate suppresses minority expression. Use this skill when the user needs to understand why certain viewpoints disappear from public discourse, evaluate the role of fear of isolation in opinion expression, or assess opinion climate dynamics — even if they say 'why are people afraid to speak up', 'silent majority', or 'social pressure on opinions'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Apply cultivation theory (Gerbner) to analyze how long-term media exposure shapes worldviews. Use this skill when the user needs to study cumulative media effects on audience beliefs, evaluate mainstreaming and resonance phenomena, or assess how media consumption patterns correlate with perceptions of social reality — even if they say 'does watching news make people more fearful', 'how does media shape worldview', or 'mean world syndrome'.".
日本語の概要は準備中です。原文の説明を表示しています。
Build and refine web UI—component structure, responsive layout, design tokens, state, and accessibility. Use for feature UI work beyond WCAG checks alone.
日本語の概要は準備中です。原文の説明を表示しています。
Draft a professional customer-facing response tailored to the situation and relationship. Use when answering a product question, responding to an escalation or outage, delivering bad news like a delay or won't-fix, declining a feature request, or replying to a billing issue.
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Affordance Theory (Gibson, 1979; Norman, 1988) to analyze the action possibilities that an artifact provides to an actor. Use this skill when the user needs to evaluate technology design from an affordance perspective, identify why users struggle with an interface, analyze IT-enabled organizational change through affordance actualization, or when they ask 'what does this technology afford', 'why can't users figure out this feature', or 'how does technology enable new practices'.".
日本語の概要は準備中です。原文の説明を表示しています。
Pre-deployment verification checklist. Use when about to ship a release, deploying a change with database migrations or feature flags, verifying CI status and approvals before going to production, or documenting rollback triggers ahead of time.
日本語の概要は準備中です。原文の説明を表示しています。
Simplify working code while preserving behavior—remove dead paths, flatten nesting, clarify names, reduce duplication. Use after features work but code feels over-engineered.
日本語の概要は準備中です。原文の説明を表示しています。
"Design effective data dashboards with proper KPI hierarchy, chart type selection, and interactive features. Use this skill when the user needs to create a dashboard, choose the right visualizations, organize metrics for different audiences, or evaluate dashboard tools — even if they say 'build a dashboard', 'our reports are confusing', 'which chart should I use', or 'executives can't find the metrics they need'.".
日本語の概要は準備中です。原文の説明を表示しています。
"Implement matrix factorization to decompose user-item interaction matrices into latent factor representations. Use this skill when the user needs scalable collaborative filtering, latent feature discovery, or dimensionality reduction for recommendation — even if they say 'SVD recommendations', 'latent factors', or 'factorize the rating matrix'.".
日本語の概要は準備中です。原文の説明を表示しています。