elan6666

byte-auto

Complete a multi-step product or project request end to end and verify the result. Use when the user asks for one-click completion, all necessary work, or persistence until the outcome is genuinely handled.

byte-code-rules

Apply Your ByteDance engineering behavior rules for writing, reviewing, refactoring, planning, or executing code in Byte OS. Use with byte-build, byte-plan, byte-review, byte-iterate, byte-auto, or any coding task to avoid overengineering, keep edits surgical, surface risky assumptions, and define verifiable success criteria.

byte-codebase-harness

Prepare a large-codebase navigation harness for Your ByteDance / Byte OS that works across Claude Code and Codex. Use when the user asks to make a repo easier for Claude/Codex to navigate, add CLAUDE.md or AGENTS.md, configure large monorepos, map a codebase, scope tests/lint by directory, reduce generated-file noise, add LSP guidance, or support subagent exploration before editing.

byte-do

Choose and execute the useful Byte capabilities for a mixed product or project request. Use when the user explicitly invokes $byte-do or asks Byte to select the workflow; focused requests should use the matching skill.

byte-iterate

Run structured Your ByteDance / Byte OS iteration loops based on review findings, real user feedback, market research, test failures, metrics, experiments, or product goals. Use when the user asks to improve, optimize, iterate, create the next version, or run multiple automatic iterations.

byte-next

Continue a Your ByteDance / Byte OS project by inferring and executing the next workflow step from `.byte-os/` state. Use when the user says next, continue, resume, proceed, or asks what to do after the current stage.

byte-shape

Shape a Your ByteDance / Byte OS project into product positioning, MVP scope, non-goals, user flows, UX structure, technical direction, metrics, OKRs, and an initial roadmap. Use after byte-start or byte-research, or when the user asks to define what the product should be before implementation.

byte-start

Start a Your ByteDance / Byte OS project from a rough idea. Use when creating a product from zero, initializing `.byte-os/`, combining discovery and research into the first foundation step, or restarting early-stage product discovery with a ByteDance-inspired project team.

byte-users

Analyze real post-build user feedback for Your ByteDance / Byte OS. Use only when a product, prototype, URL, screenshot, recording, analytics export, interview notes, survey results, support tickets, reviews, or other real user evidence is available. Do not use for simulated personas.

byte-build

Implement or change a codebase, document, prototype, or other deliverable and verify it. Use when the user asks to build, fix, integrate, or execute an existing plan.

byte-plan

Create an appropriately detailed execution plan. Use when the user explicitly asks for a plan, roadmap, implementation approach, sequencing, dependencies, or acceptance criteria before execution.

byte-brainstorm

Generate and compare distinct product, feature, or strategy directions. Use when the user explicitly asks to brainstorm, expand options, or escape a prematurely fixed solution.

byte-discuss

Clarify requirements, tradeoffs, or direction without implementing. Use when the user asks to discuss first, compare choices, resolve ambiguity, or confirm scope.

byte-future

Record an idea for later without adding it to current scope. Use when the user says save for later, parking lot, not now, or remember this without implementing it.

byte-research

Research current evidence that can change a decision. Use when the user asks for research or comparison, or when an important project choice depends on external facts that may be current or uncertain.

byte-review

Review a product, implementation, plan, or deliverable for material issues and readiness. Use when the user asks for review, audit, critique, quality assessment, or what should change next.

byte-status

Inspect and summarize the real current state of a project. Use when the user asks for progress, status, blockers, what remains, what is actually complete, or the best next action.

byte-deliver

Package final Your ByteDance / Byte OS delivery artifacts. Use when the product has been built and reviewed, or when the user asks to ship, hand off, summarize, package, or produce final delivery instructions.