tt-a1i
- 53 skills
- 0 followers
- 194 repo stars
- last month last updated
- ▌ Loop Me 2 · tt-a1i bundleGrill me about specs for the workflows I want to build, within this workspace.
- ▌ Claude Handoff 2 · tt-a1i bundleHand the current conversation off to a fresh background agent that picks up the work immediately.
- ▌ Agents Market Installer 3 · tt-a1iUse when a user asks Claude Code to recommend, install, update, or inspect specialized coding subagents for Claude Code, Codex, OpenCode, or multiple targets in the current repository.
- ▌ First Principles Thinking 2 · tt-a1i bundleThis skill should be used when the user asks to "analyze from first principles", "第一性原理", "从根本分析", "从零开始思考", "think from scratch", "question this design", "这个设计合理吗", "is this the right approach", "为什么要这样做", "why are we doing it this way", "有没有更好的方案", "is there a better solution", "challenge assumptions", "挑战假设", or needs to evaluate architectural decisions, design choices, or problem-solving approaches without relying on analogies or conventions.
- ▌
- ▌
- ▌
- ▌
- ▌ Loop Me · tt-a1i bundleGrill me about specs for the workflows I want to build, within this workspace.
- ▌ Claude Handoff · tt-a1i bundleHand the current conversation off to a fresh background agent that picks up the work immediately.
- ▌ Agents Market Installer 2 · tt-a1iUse when a user asks Claude Code to recommend, install, update, or inspect specialized coding subagents for Claude Code, Codex, OpenCode, or multiple targets in the current repository.
- ▌
- ▌ Mcporter · tt-a1iUse the mcporter CLI to list, configure, auth, and call MCP servers/tools directly (HTTP or stdio), including ad-hoc servers, config edits, and CLI/type generation.
- ▌
- ▌
- ▌
- ▌
- ▌ Agent Inspect · tt-a1iUse this skill whenever the user asks to inspect, audit, review, assess, or evaluate a codebase/project for maintainability, extensibility, architecture, reliability, security, testing, engineering quality, or AI-agent/prompt/tooling risks. Also use this when invoked by `/inspect`. It performs a read-only, evidence-backed, multi-agent project inspection with complete file coverage, per-dimension scoring, blunt technical findings, and explicit degraded-mode disclosure.
- ▌ Codex Task Messenger · tt-a1i bundleCommunicate between existing local Codex App tasks that share one working directory. Use when the user asks to list or inspect same-directory tasks, send one a message or context handoff, ask a task to return a result, wait for that result, continue a request that needs user input, present an inbound task reply, or explicitly broadcast a one-way notice. Also use for Codex delegations that invoke $codex-task-messenger or contain its message-card metadata.
- ▌ Idea Finder · tt-a1i bundleOrchestrate evidence-native demand research through the standalone idea-finder CLI. Use when a user asks Codex or another compatible agent to discover or investigate demand, inspect stored evidence, compare qualitative and quantitative signals, handle incomplete research, calibrate an Opportunity, plan or record validation work, or configure recurring monitoring.
- ▌ Codex Web Bridge · tt-a1i bundleBridge Codex to web-based AI model products by packaging local task context, scrub-checking it, sending it through an approved browser surface to ChatGPT Pro, Claude, Grok, Gemini, or another web model, waiting for the answer, and returning the model response to the user or Codex. Also guide DevSpace-like MCP Connector Mode when the user wants ChatGPT Pro or another MCP-capable web host to access approved local workspaces without relying on Codex browser automation. Use when the user asks for GPT Pro, ChatGPT Pro, Claude web, Grok, Gemini web, web model bridge, external model consult, ask another model, second opinion, use a web AI model, browserless agent access to GPT Pro, MCP connector, DevSpace-like workflow, or send local repo context to a browser-based model for planning, review, debugging, architecture discussion, or implementation guidance.
- ▌ Reason Through · tt-a1i bundleAnalyze an idea, proposal, change, claim, or decision from facts through problem, value, mechanism, consequences, evidence, alternatives, and action. Use when the user asks what something is for, why it matters, whether it is worth doing, what impact it has, or how to decide. Do not use for simple factual lookup or straightforward execution.
- ▌ Repo Learning · tt-a1i bundleTurn a Git repository URL or local path into one elegant, self-contained HTML learning page that teaches the project's value, architecture, and operating principles top-down with diagrams. Use when the user wants to understand, learn, onboard, explain, map, or study a repository.
- ▌ Simplify Codebase · tt-a1i bundleSimplification audit or authorized codebase simplification whose stated objective is to remove accidental complexity. Use for evidence-backed deletion or consolidation of dead code, duplicate state, redundant APIs or layers, ownerless abstractions, obsolete compatibility or design records, and over-engineering in any language; also use for 代码简化 or 熵回收. Do not use for general code review, onboarding, style-only refactoring, or performance tuning.
- ▌ Agents Market Installer · tt-a1iUse when a user asks Codex to recommend, install, update, or inspect specialized coding subagents for Claude Code, Codex, OpenCode, or multiple targets in the current repository.
- ▌ Subagents · tt-a1i bundleInvoke this skill when the user asks to use subagents or when a substantial, self-contained task can run independently in the background.
- ▌ Workflows · tt-a1i bundleOrchestrates multi-agent work with OpenPI's inline JavaScript Workflow DSL. Use when a task needs multi-phase fan-out, pipelines, barriers, structured handoffs, or resumable background orchestration.
- ▌ Background Terminals · tt-a1iRun and manage long-lived shell commands in background terminals. Use for dev servers, watchers, streaming builds, and other commands that should keep running while the agent continues working.
- ▌
- ▌ Using Harnessed · tt-a1i bundleUse at the start of every session and before completing any coding task.
- ▌ Contract Writing · tt-a1i bundleUse before starting any coding task when Superpowers is not present.
- ▌
- ▌
- ▌
- ▌ Kanban Video Orchestrator · tt-a1i bundlePlan, set up, and monitor a multi-agent video production pipeline backed by Hermes Kanban. Use when the user wants to make ANY video — narrative film, product/marketing, music video, explainer, ASCII/terminal art, abstract/generative loop, comic, 3D, real-time/installation — and the work warrants decomposition into specialized profiles (writer, designer, animator, renderer, voice, editor, etc.) coordinated through a kanban board. Performs adaptive discovery to scope the brief, designs an appropriate team for the requested style, generates the setup script that creates Hermes profiles + initial kanban task, then helps monitor execution and intervene when tasks stall or fail. Routes scenes to whichever Hermes rendering / audio / design skill fits each beat (`ascii-video`, `manim-video`, `p5js`, `comfyui`, `touchdesigner-mcp`, `blender-mcp`, `pixel-art`, `baoyu-comic`, `claude-design`, `excalidraw`, `songsee`, `heartmula`, …) plus external APIs for TTS, image-gen, and image-to-video as needed.
- ▌
- ▌ Grilling · tt-a1i bundleGrill 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.
- ▌ Roundtable · tt-a1i bundleConvene a roundtable of sub-agents that debate a decision or proposal from opposing perspectives — parallel independent statements, anonymous cross-review, then a chaired verdict reporting consensus and dissent.
- ▌ To Tickets · tt-a1i bundleBreak a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
- ▌ Goal Crafter · tt-a1i bundleCraft verifiable, tight goal prompts for AI coding agents (Claude Code /goal, Codex Automations, Pi), either from a standalone task interview or from an already-approved to-goal handoff. Use when the user says "给我一个 goal 提示词", "帮我写个 goal", "设置一个自动化任务", "我想让 agent 自动做 X", or asks to turn a task into a self-running loop. Ensures every goal has a checkable completion criterion so the agent knows when it's done.
- ▌ Spec Executor · tt-a1i bundleExecute the latest approved SPEC READY from an inherited or forked conversation, keeping implementation work out of the planning thread. Use after to-spec when the final spec fits one implementation session and the new thread should implement, test, review, and return a structured receipt without rewriting a to-goal handoff. Do not use for unresolved specs, multi-session builds, parallel handoffs, or context that needs compression; use to-tickets or to-goal for those.
- ▌ Execute Spec In Fork · tt-a1i bundleOrchestrate one approved SPEC READY through a same-directory Codex App fork: create and name the execution task, ask it to run spec-executor, route decisions through Codex Task Messenger, validate the returned receipt, and archive a completed child. Use only when the user explicitly asks to execute an approved spec in a fork, or when handling a Messenger reply, resume, or recovery event for an execution fork this skill launched. Requires Codex App native task tools and codex-task-messenger; use the manual fork plus spec-executor route elsewhere.
- ▌ Setup Matt Pocock Skills · tt-a1i bundleConfigure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
- ▌ Resolving Merge Conflicts · tt-a1i bundleUse when you need to resolve an in-progress git merge/rebase conflict.
- ▌ Improve Codebase Architecture · tt-a1i bundleScan a codebase for deepening opportunities, present them as a report — HTML on request — then grill through whichever one you pick.
- ▌ Triage · tt-a1i bundleMove issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.
- ▌ To Goal · tt-a1i bundleTurn an approved spec, agent-ready ticket, tracker frontier, or partially implemented ticket into a verifiable execution goal without re-interviewing the user. Use after to-tickets or triage, before starting a fresh implementation session; use --all only for an explicitly requested cross-ticket goal.
- ▌ To Spec · tt-a1i bundleTurn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
- ▌ Ask Matt · tt-a1i bundleAsk which skill or flow fits your situation. A router over the skills in this repo.
- ▌ Handoff · tt-a1i bundleCompact the current conversation into a portable handoff document, with an optional live clarification path for compatible Codex tasks.
- ▌ Skillroster · tt-a1i bundleInspect and govern local Skills: inventory, usage evidence, duplicates, broken links, Core/On-demand proposals, Plans, Receipts, Apply, and Undo. Also find a specialized local Skill when the user requests one or the task would benefit from instructions beyond the visible catalog. Ordinary work can proceed with the Agent's existing capabilities. Not for installing third-party Skills or migrating, distributing, synchronizing, or repairing shared Skill-manager directories.
- ▌ First Principles Thinking · tt-a1i bundleThis skill should be used when the user asks to "analyze from first principles", "第一性原理", "从根本分析", "从零开始思考", "think from scratch", "question this design", "这个设计合理吗", "is this the right approach", "为什么要这样做", "why are we doing it this way", "有没有更好的方案", "is there a better solution", "challenge assumptions", "挑战假设", or needs to evaluate architectural decisions, design choices, or problem-solving approaches without relying on analogies or conventions.
- ▌ Archify · tt-a1iCreate polished, validated architecture, workflow, sequence, data-flow, and lifecycle/state diagrams as explorable standalone HTML with inline SVG, dark/light themes, optional trace motion, and PNG/JPEG/WebP/SVG/WebM export. Accept plain-language requirements or pasted Mermaid flowchart, sequenceDiagram, and stateDiagram input; inspect repository evidence when the diagram must reflect real code. Use when the user asks to visualize system architecture, infrastructure, cloud/security/network topology, technical workflows, API call sequences, request lifecycles, data pipelines, ETL/ELT, data lineage, state machines, or to convert/beautify Mermaid.