Vibe Prompt Compiler Portable

Turn rough implementation requests into portable coding briefs that can be pasted into almost any AI coding tool.

Default Behavior

Use this skill automatically when a user gives a vague coding request. Do not require the user to run scripts first.

Instead:

1. 1. Classify the request.
2. Extract the facts already present.
3. Turn missing details into explicit assumptions.
4. Compile a clean internal implementation brief.
5. Use that brief as the source of truth for the coding response.

Only mention scripts when the user wants portability, reusable CLI commands, or a saved handoff for another tool.

Task Types

Classify into one of these:

• - INLINECODE0
• INLINECODE1
• INLINECODE2
• INLINECODE3
• INLINECODE4
• INLINECODE5
• INLINECODE6
• INLINECODE7
• INLINECODE8
• INLINECODE9
• INLINECODE10
• INLINECODE11

Use the narrowest obvious type. Only ask a follow-up question when one missing detail blocks useful progress.

Portable Defaults

Unless the user says otherwise:

• - prefer MVP over over-engineering
• prefer minimal diffs over broad rewrites
• do not modify unrelated files
• avoid adding dependencies unless justified
• make assumptions explicit
• keep outputs easy to test and verify
• state non-goals when they reduce drift
• prefer evolutionary changes over rewrites for existing systems
• separate current-task execution from future-state ideas

Main Commands

Default: compile mentally and use the structure directly in the answer or coding workflow.

Compile a prompt via CLI when needed:

INLINECODE12

Create a handoff brief:

INLINECODE13

Extract repository-aware rules:

INLINECODE14

Useful flags:

• - INLINECODE15
• INLINECODE16
• INLINECODE17
• INLINECODE18
• INLINECODE19
• INLINECODE20
• INLINECODE21
• INLINECODE22
• INLINECODE23
• INLINECODE24
• INLINECODE25
• INLINECODE26

Target Tool Usage

When the request is broad, architectural, or likely to drift, prefer creating a handoff-style brief over answering from the raw request.

Cursor / VS Code chat

• - run compile_prompt.py or INLINECODE28
• paste the output into the chat
• let the tool implement only the current slice

Claude Code / Codex CLI / Gemini CLI

• - use the compiled prompt or handoff as the source of truth
• ask the coding tool to plan first for broad tasks
• ask for minimal fixes for bug work
• prefer --target-tool, --ruleset, and repo-aware flags for stronger execution constraints

Publish Notes

This skill is now suitable for sharing as a portable coding-brief compiler with:

• - structured prompt compilation
• stronger execution handoffs
• Chinese-first output
• tool-specific presets
• development rulesets
• repository-aware rule extraction and merging
• regression coverage across routing, golden outputs, presets, linting, and repo-aware flows

References

• - Read references/auto-mode.md first for the default automatic behavior.
• Read references/templates.md for prompt skeletons.
• Read references/routing.md when classification is unclear.
• Read references/usage.md for suggested workflows in common IDEs and coding tools.
• Read references/tool-examples.md for concrete examples in Cursor, Claude Code, Codex CLI, and Gemini CLI.
• Read references/real-examples.md for realistic request-to-brief transformations, especially for architecture, integration, workflow, and vague coding requests.