「cis」の検索結果

Use while deriving cases - Given/When/Then and the techniques (partitions, boundaries, decision tables, state transitions) that find the cases the criteria do not state

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

Use when starting a backend task that could be built in either language - decide Go vs Java (Quarkus/Spring) from the task's shape and the repository's existing stack

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

Use before handing off any change to an endpoint, job or migration — start the service from the task branch and exercise the change with real requests, real logs and real DB side effects

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

Phase E of a WinForms-to-Avalonia migration: verify behavioral parity against Phase A contracts, record intentional differences, validate supported environments and packaging, and make evidence-based legacy cutover decisions. Use only for an explicit migration when comparing the legacy and Avalonia implementations or when the orchestrator routes here. Do not delete legacy without the cutover checklist and explicit authorization.

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

Generate operations runbooks and post-mortems for incident response — severity matrix, decision trees, escalation paths, war room setup (Slack/Zoom), status page updates, customer comms templates, and blameless post-mortems with action items.

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

Persistent memory across AI sessions using ChromaDB vector database. Stores and retrieves context from past conversations, decisions, and code. Use when user asks to remember something, search past conversations, recall what was done before, save context for later, or find information from previous sessions. Do NOT use for git history or file-based notes.

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

Run structured brainstorming sessions (divergent/convergent), improve prompts with 7-dimension framework, and apply decision frameworks (RICE, weighted scoring, first principles, pre-mortem).

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

Encode Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great. From the creator of Sonner (13M+ weekly npm downloads), Vaul, animations.dev, and Linear's web team. Use when user wants to polish UI, audit animations, review component interactions, add micro-feedback, or elevate motion quality.

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

Use only after explicit Codex `$superloopy:say-it-straight` or Claude Code `/superloopy:say-it-straight` invocation to make supplied or requested prose direct, concise, and natural without changing facts or protected text.

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

Rigorous engineering orchestrator ported from Lauren Tan's pstack (poteto-mode): reads your task, picks one of 23 playbooks (bug fix, feature, refactoring, perf, investigation, prototype, babysit, shipping, autonomous run, orchestrate, and more), routes to bundled procedures (how, why, architect, arena, swarm, interrogate, unslop, technical-writing, show-me-your-work, tdd, and others), and applies 24 engineering principles. Self-contained: no plugin install, no sibling skills required, works with any agent that reads skills.sh-format SKILL.md files. Use whenever a task needs rigor: nontrivial code changes, architecture decisions, debugging, reviews, PRs, long autonomous runs, or "work like poteto", "poteto-mode", "pstack".

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

用户在做决策时不确定自己是否真的理解某个领域，或准备进入一个看似熟悉但缺乏验证记录的领域时。 语言信号："我觉得我懂这个行业"/"这个看起来很简单"/"别人都在投这个"/"我来研究一下这个新领域" 不适用于：纯信息查询、日常琐事选择、用户已有充分专业知识的领域。

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

用户准备做出一个重大决策（投资/收购/承诺），需要评估下行保护是否充足时。或在估值不确定时决定是否行动。 语言信号："这个价格够不够低"/"万一判断错了怎么办"/"我能承受多少亏损"/"下行空间有多大" 不适用于：日常低风险决策、纯上行分析（不关心下行保护时）。

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

Generate traceability matrix and quality gate decision. Use when the user says "lets create traceability matrix" or "I want to analyze test coverage"

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

When the user wants help with pricing decisions, packaging, or monetization strategy. Use when the user mentions 'pricing,' 'pricing model,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'pricing strategy,' 'pricing experiments,' 'price anchoring,' 'enterprise pricing,' 'GTM pricing,' 'price setting,' 'value-based pricing,' 'revenue optimization,' or 'pricing psychology.' This skill covers pricing research, tier structure, packaging strategy, discount frameworks, upsell mechanics, and pricing experiments.

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

The judgment layer: when AutoCode acts on its own and when it stops and asks, and how it speaks about decisions and money. iLang v5.0: perception sets the 11 dimensions, the frozen reference function f_v5 sets the mode, the user sees one plain line. Runs before every consequential action.

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

Structured pre-design questioning to surface hidden constraints before any architecture decision is locked in. Forces the architect/auditor/reviewer to enumerate what they DON'T know before proposing.

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

How to write — and how to use — a skill that IS one aesthetic rather than a catalogue of them. A catalogue lets an agent pick, and it picks the modal option; a committed aesthetic makes it execute one thing precisely, against rules you can check. Use when a design keeps coming out competent and forgettable, when starting a new brand surface with no reference, or when authoring a house style you want executed the same way twice.

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

Store a fact, preference, decision, note or file permanently in the Cognee knowledge graph, tagged as user, project or agent. Plain "remember this" requests go here, not to Claude's built-in memory.

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

Guides user research and research ops. Use when running interviews, usability tests, surveys, or synthesis to de-risk product decisions; not experiments or review mining.

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

Chooses under uncertainty: value of more data, cost-based thresholds, abstention, when to stop a test and ship, robust choice. Use when deciding, not estimating.

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

Evidence-driven web and open-source research for questions that require multiple sources, factual verification, comparisons, or an adopt/adapt/build decision. Use for substantial research in foreground sessions, the genesis-researcher subagent, and research-profile background sessions. Skip for a single stable fact or a known URL that only needs fetching.

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

Writes or updates engineering documentation and architecture decision records from repository facts, explicit assumptions, trade-offs, and verification links. Use for README changes, design docs, runbooks, ADRs, migration notes, and contributor documentation. Not for implementation planning alone or for copying external documentation without provenance.

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

Grounds version-sensitive engineering decisions in authoritative current sources by detecting the installed stack, retrieving official documentation or source, reconciling conflicts, and recording citations and confidence. Use for framework APIs, dependency behavior, standards, compatibility, migrations, or technical recommendations that may have changed. Not for stable project-local logic or broad product discovery.

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

Fast sprint status check. Reads the current sprint plan, scans story files for status, and produces a concise progress snapshot with burndown assessment and emerging risks. Run at any time during a sprint for quick situational awareness. Use when user asks 'how is the sprint going', 'sprint update', 'show sprint progress'.

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