「decision」の検索結果

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

日本語の概要は準備中です。原文の説明を表示しています。

Solves UI lock-in. Reverse engineers your existing UI, strips all layout/token decisions, preserves every hook, handler, and API call untouched, then rebuilds the UI from scratch with a fresh design system. Use /ui-restructure to fully redesign, --style apple|linear|minimal|dashboard for named styles, --mode layout|theme|grid for partial rebuilds, --god-mode to redesign from the user's perspective using 100-user mindset simulation and 6 UX principles, --keep-tokens to preserve your token system, --prompt for custom redesigns. Applies mandatory world-class polish: spring motion, 5-state micro-interactions, 8pt spacing grid, WCAG accessibility. Supports Next.js, React, Vue 3, Tailwind, CSS Modules, styled-components, shadcn.

日本語の概要は準備中です。原文の説明を表示しています。

Turn a meeting transcript into clean notes, the decisions, and who does what by when, then draft the follow-up mail and send it only after your GO. Use for "meeting notes", "action items from this meeting", "who did what in this transcript", "who does what after the call".

日本語の概要は準備中です。原文の説明を表示しています。

Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying.

日本語の概要は準備中です。原文の説明を表示しています。

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

日本語の概要は準備中です。原文の説明を表示しています。

A relentless interview to sharpen a plan or design before committing to an approach. Use on any "grill me" or "grill this plan" trigger phrase, when the user asks to stress-test a decision, plan or design, and before handing a finished plan off to a startcycle run or a plan-canvas review.

日本語の概要は準備中です。原文の説明を表示しています。

Experimental workflow for summarizing work that still needs human judgment across configured pull requests, issues, feedback, errors, and delivery signals. Use for a human decision queue or bounded review.

日本語の概要は準備中です。原文の説明を表示しています。

Experimental workflow for reviewing configured repositories' pull requests. Use for manual or scheduled PR triage, approval, or merge decisions.

日本語の概要は準備中です。原文の説明を表示しています。

Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.

日本語の概要は準備中です。原文の説明を表示しています。

Use when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).

日本語の概要は準備中です。原文の説明を表示しています。

API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.

日本語の概要は準備中です。原文の説明を表示しています。

Use before starting any significant build or before shipping: problem-framing pre-flight, one-way/two-way door classification, ADR-lite decision logging, and post-ship outcome loop. Complements godmode-shipping (technical gate) and bdbresilience (error recovery).

日本語の概要は準備中です。原文の説明を表示しています。

A skill for AI agents that want to produce better daily reports and discover more of what their users actually want. Scans source front pages, diffs them against yesterday, prescreens with a weighted profile, reviews with an LLM, deduplicates, publishes, and evolves the profile from user feedback. All decisions go to an append-only tape for audit and replay.

日本語の概要は準備中です。原文の説明を表示しています。

Diagnose App Store submission blockers and operate review health with asc, including readiness validation, repair routing, status monitoring, cancellation, and retry decisions. Use when validation fails, a version is not in a valid state, review status is unclear or stuck, or a failed submission must be repaired and retried. For staging, upload, publication, and submission execution, use asc-release-flow.

日本語の概要は準備中です。原文の説明を表示しています。

Design thinking and taste-building principles based on Dieter Rams. Use when making design decisions, reviewing UI quality, or building taste for any visual interface — web or native.

日本語の概要は準備中です。原文の説明を表示しています。

Orchestrate App Store releases with asc, including staging a version, uploading or building an artifact, publishing, and submitting for review. Use when the user wants to prepare or execute a release. Keep Game Center item preparation in this skill; route other readiness failures, stuck submissions, cancellation, and retry decisions to asc-submission-health.

日本語の概要は準備中です。原文の説明を表示しています。

Applies Chesterton's Fence, Occam's Razor, the Peter Principle, and Dunning-Kruger to technical decisions. Use before refactoring, architectural changes, or any task where changing existing behavior carries risk or requires judgment about what the user actually needs.

日本語の概要は準備中です。原文の説明を表示しています。

Stress-tests ideas by surfacing assumptions, counterarguments, and confidence gaps. Use when evaluating claims, proposals, plans, or decisions that need rigorous intellectual scrutiny.

日本語の概要は準備中です。原文の説明を表示しています。

Combine React's official "You Might Not Need an Effect" guidance with this project's stricter no direct useEffect stance. Use when writing, reviewing, or refactoring React components that might reach for useEffect, derived state, event relays, reset logic, subscriptions, or client fetching.

日本語の概要は準備中です。原文の説明を表示しています。

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

日本語の概要は準備中です。原文の説明を表示しています。

Use when: 'intake this repo/skill', 'evaluate external skill', 'should we adopt X', a candidate repo URL plus an adoption question, or any external skill/workflow/tool surfaces as a possible fit for Agistra. Structured front-door evaluation of external skills, workflows, and similar capability artifacts before any install, promotion, or adaptation decision. Ends in exactly one classification: Install candidate, Adapt concept, or Reject. Never install first — intake first.

日本語の概要は準備中です。原文の説明を表示しています。

Use when: architecture mode, architect this, ADR, C4, PlantUML, system boundary, design decision, PRD gap, high ambiguity, multiple technical approaches, security architecture, data architecture, integration risk, implementability gap, story ticket, or epic ticket.

日本語の概要は準備中です。原文の説明を表示しています。

Workflow-state classification vocabulary for inter-team relay. Maps inbound signals from the remote agent to a routing decision. Intentionally narrow — states and destinations only.

日本語の概要は準備中です。原文の説明を表示しています。

One-question-at-a-time design interrogation. Use when: 'grill me', 'interrogate this', 'one question at a time', 'brainstorm', 'let's brainstorm', 'let's discuss', or design review start. Produces ADRs and glossary as decisions settle. Do not use for settled designs — load architecture-mode instead.

日本語の概要は準備中です。原文の説明を表示しています。