「new」の検索結果

Merge duplicate or excessively overlapping beads in .beads/beads.jsonl into canonical ones. Run after any batch where 20+ new beads were created.

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

End-of-session ritual. Close finished beads, file new ones for remaining work, run verify, commit in logical groupings, push. Work is not complete until git push succeeds.

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

Scaffold a new Forge subagent (planner/architect/executor/reviewer/debugger/memory-style).

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

30 → 5 → 15 funnel for brainstorming new features on the existing Forge codebase. Use when adding capability to a mature install, not for greenfield.

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

Scaffold a new model provider for Forge — class implementation, registry wiring, providerEnum entry, local-catalog classification, and unit test with mocked transport. Use for anything under src/models/.

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

End-of-session ritual — close finished beads, file new ones for remaining work, run verify, commit in logical groupings, push. Work is not complete until git push succeeds.

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

Scaffold a new model provider for Forge — class, registry wiring, providerEnum entry, local-catalog classification, router check, and a unit test with mocked transport.

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

Scaffold a new Forge tool end-to-end — type, implementation, registration, permission/risk classification, and unit test. Use when adding anything to src/tools/.

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

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Interpreter's capabilities with specialized knowledge, workflows, or tool integrations.

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

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.

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

Build and maintain a persistent, interlinked markdown wiki (second brain / research notebook / personal knowledge base) from raw sources. Use this skill when the user wants to ingest an article / paper / note / URL / PDF into their wiki, ask a question against their wiki, lint/health-check their wiki, or set up a new wiki from a folder. Triggers include phrases like "add this to my wiki", "ingest this", "file this article", "update my notes with this", "what does my wiki say about X", "health-check my wiki", "find stale/orphan pages", or any workflow involving a `raw/` source folder, `wiki/` markdown folder, `index.md`, or `log.md`. Compatible with Obsidian vaults.

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

Ingest one new source into an existing persistent markdown wiki or established vault workflow. Use this when the user asks to add an article, PDF, note, URL, transcript, or other source into their wiki and wants the source filed, linked, indexed, and logged. If the wiki workflow does not exist yet, use $wiki-bootstrap first. This skill is for the ingest operation only.

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

Create a new Remotion video

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

Take one new feature slice from idea to reviewed, committed code in a single guided pass — scope it into the smallest shippable slice, build it test-first with strict TDD, review and fix the diff, then commit it. Chains slice → test-driven-development → the built-in /code-review → git-commit. Not for reviewing an existing PR, upgrades, or open-ended design questions.

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

Strict red-green-refactor TDD workflow for implementing features, fixing bugs, or changing behavior in Rails applications. Enforces the discipline of writing a failing test before any production code. Use whenever you want to implement with TDD — whether a new feature, a bugfix, a refactor, or any behavior change.

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

Unwraps hard-wrapped markdown files so that each sentence ends with a newline instead of mid-sentence line breaks. Joins continuation lines within a paragraph into single lines, then re-breaks at sentence boundaries (period, question mark, exclamation point). Preserves blank lines, headings, fenced code blocks, block quotes, and list items. Use when asked to unwrap text, fix line breaks, reflow sentences, or clean up hard-wrapped markdown or .qmd files.

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

Use for every answer. After the final answer, append a new line that starts with exactly "RECEIPT:" followed by a three-word note. This proves the skill was loaded by the runtime.

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

Use when asked to brainstorm, evaluate whether an idea is worth building, run office hours, or think through a new product idea or design direction before any code is written.

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

"Apply Sociotechnical Systems Theory to analyze and design work systems through joint optimization of social and technical subsystems. Use this skill when the user needs to diagnose why a technology implementation disrupted work practices, design IT-enabled work systems that balance human and technical needs, or when they ask 'why did this system hurt productivity despite being technically sound', 'how do we design work around new technology', or 'why are people resisting this technically superior system'.".

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

"Apply the Theory of Planned Behavior to predict behavioral intentions from attitudes, subjective norms, and perceived behavioral control, and identify intervention leverage points. Use this skill when the user needs to predict adoption of a new behavior, diagnose why an intended behavior does not occur, design behavior change campaigns, or when they ask 'why do people not follow through', 'what predicts behavior change', or 'how to increase adoption rates'.".

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

"Apply the Technology Acceptance Model (Davis, 1989) and Unified Theory of Acceptance and Use of Technology (Venkatesh et al., 2003) to predict technology adoption. Use this skill when the user needs to evaluate user acceptance of a new system, diagnose adoption barriers, design interventions to improve technology uptake, or when they ask 'why aren't users adopting this', 'what drives technology acceptance', or 'how do we increase adoption rates'.".

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

"Apply organizational ecology (Hannan and Freeman) to analyze population-level dynamics of organizational founding, failure, and selection. Use this skill when the user needs to explain industry-level patterns of birth and death rates, analyze structural inertia and liabilities of newness or aging, evaluate why adaptation is rare relative to selection, or when they ask 'why do most startups fail', 'why is this industry dominated by old firms', or 'why do organizations resist change despite environmental pressure'.".

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

"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'.".

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

"Apply the Bass Diffusion Model (1969) to forecast innovation adoption using innovation and imitation coefficients. Use this skill when the user needs to forecast new product adoption curves, estimate market penetration timing, calibrate launch strategy based on diffusion dynamics, or when they ask 'how fast will this spread', 'when does adoption take off', or 'what is the expected S-curve'.".

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