7,589 件 ・ 関連度順
概要と使いどころ
Bruno is an open-source, offline-first API client that stores collections as plain-text .bru files on your filesystem. It serves as a privacy-focused, git-friendly alternative to Postman and Insomnia with no cloud sync and no account required.
日本語の概要は準備中です。原文の説明を表示しています。
Use Bats-core when an agent needs to turn fragile shell scripts or command-line workflows into something it can verify repeatedly after edits. The agent writes focused Bash tests for success paths, failure paths, and output contracts, then runs them locally or in CI before a refactor, release, or incident fix goes out.
日本語の概要は準備中です。原文の説明を表示しています。
Read the public web: search for sources, read one page as Markdown, and run site scripts for structured records (X/Twitter via FxEmbed, Exa search, GitHub, Hacker News, Reddit, Wikipedia, Bilibili bundled; a catalog of more installable with one command). Use for any task that needs something from a public website: a topic without a URL, a URL to read, a site's records (a tweet, a timeline, a repo's stats, a front page, a ranking), or a page that only renders with JavaScript.
日本語の概要は準備中です。原文の説明を表示しています。
Decide what to borrow, adapt, or write before building something. Use when the user describes an app, tool, CLI, or feature they want to build and needs to know which parts already exist as open-source GitHub repos (BORROW), which are worth reading and adapting (KITBASH), and which to just write (WRITE). Every repository named is checked against the live GitHub API, so invented ones never reach the user.
日本語の概要は準備中です。原文の説明を表示しています。
Expert product strategist for vision, strategy, and market positioning. Use when defining product vision, assessing product-market fit, sizing market opportunities (TAM/SAM/SOM), competitive positioning, or choosing between build/buy/partner. Covers business model design, monetization strategy, platform decisions, and strategic roadmap planning.
日本語の概要は準備中です。原文の説明を表示しています。
Design a tdmcp feature into an implementable spec before any code is written — choose the layer, define the Zod input schema, lay out the TD network topology, plan the bridge/Python approach, sketch a UI wireframe when relevant, and list probe-first risks + the test plan. Use whenever a tdmcp feature idea needs a design/wireframe/spec, or when someone asks to plan/scope/architect a new tool, generator, effect, control, or AI prompt for the TouchDesigner MCP server.
日本語の概要は準備中です。原文の説明を表示しています。
Template skill for a leadership-transition / executive cockpit — when someone steps into or covers a leadership role and needs to not drop anything. Produces a handoff doc + decision-rights map, an "open loops" tracker, a team-comms cadence, and a recurring report/update drafter. Trigger on "/exec-cockpit", "handoff doc", "decision-rights map", "open loops tracker", "cover for <role>", "interim <role>". Customize the placeholders to your situation.
日本語の概要は準備中です。原文の説明を表示しています。
Use on Day 1 of an AIS-OS install, when someone says "set me up", "onboard me", "let's get started", "fill in my AIOS", or has just cloned the kit. Combined wizard — runs the 7-question intake AND scaffolds the Day-1 file set at the end. Idempotent — re-run any time after editing aios-intake.md.
日本語の概要は準備中です。原文の説明を表示しています。
Use when someone asks for an AIOS audit, asks to score their setup against the Four Cs, or says "is my AIOS working" / "audit my setup" / "find gaps in my AIOS". Produces a Four-Cs scoreboard with top-3 fixes ranked by leverage.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks a question about how things in the codebase or wiki relate — what connects two things, how something works end to end, what depends on what, or what a concept means in this repo. Answers from the knowledge graph in graphify-out/graph.json, with source-location citations. Trigger on "/graph-query", "ask the graph", "what connects X to Y", "trace how X works", "explain <concept> from the graph", "shortest path between".
日本語の概要は準備中です。原文の説明を表示しています。
Rewrites code to its simplest possible form while preserving exact external behavior (KISS, YAGNI).
日本語の概要は準備中です。原文の説明を表示しています。
Produces a rigorous, forward-looking technical audit with severity ratings and improvement directions.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic root-cause isolation and minimal fix proposal for software bugs.
日本語の概要は準備中です。原文の説明を表示しています。
Systems-level performance engineer: identifies hotspots, provides optimized code with resource justifications.
日本語の概要は準備中です。原文の説明を表示しています。
Breaks down complex tasks into ordered, verifiable sub-tasks with dependencies, milestones, and risks.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes a project description and outputs a structured bid: scope, effort, tech risks, and optional pricing.
日本語の概要は準備中です。原文の説明を表示しています。
Enforces decisive execution without confirmation requests; suppresses redundant explanations and prioritizes direct action.
日本語の概要は準備中です。原文の説明を表示しています。
Writing engine that audits and rewrites prose for AI-resistance, fidelity, and mechanical tell removal.
日本語の概要は準備中です。原文の説明を表示しています。
Evaluates open-source packages: health, suitability, dependency risk, and in-house alternatives.
日本語の概要は準備中です。原文の説明を表示しています。
Automatically routes requests to the correct skill (Planner, Debugger, Advisor, etc.) based on first message content.
日本語の概要は準備中です。原文の説明を表示しています。
Generates or fills gaps in project documentation (README, AGENTS.md, /docs, inline comments).
日本語の概要は準備中です。原文の説明を表示しています。
Produces a concise, structured analysis report of a codebase: dependencies, workflow, and context.
日本語の概要は準備中です。原文の説明を表示しています。
Creates or completes a medium-coverage test suite: unit, component, and critical e2e flows.
日本語の概要は準備中です。原文の説明を表示しています。
Build UI interactions whose motion comes from a physical model instead of durations and easing curves. Turn a feel described in words ("a toggle that feels heavy", "a drawer with a magnetic snap", "a card you throw into a corner", "a knob with heavy detents", "a sticky slider") into a production component driven by mass, stiffness, damping and force fields (magnets, friction, walls), on a line, in a plane or around a dial, plus a test rig that plots position, velocity and the force field, overlays the model's prediction on the measured motion, and exports the same spring to Framer Motion, react-spring, SwiftUI, Compose or CSS linear(). Use this whenever someone asks for an animation, transition, spring, gesture, drag, flick, snap points, bottom sheet, toggle, slider, carousel or any micro-interaction that should "feel" a certain way, or wants to tune or explain a spring, even if they never say "physics".
日本語の概要は準備中です。原文の説明を表示しています。