メニュー
Enable strict coding discipline (Karpathy Guidelines). Use when you want the AI to be extra careful about simplicity, assumptions, and surgical changes. Toggle on at session start or before complex work.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/markster-public/markster-os --skill karpathyコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Writes funnel assets step by step from a completed funnel plan. Process covers VSL script, landing page copy, OTO sequences, email nurture, and application page. Use when creating funnel copy after architecture is confirmed, or when you need to write VSL, landing page, or email assets from a defined offer. Run after funnel-plan. Triggers on "write the funnel", "build the funnel assets", "write the VSL", "write the landing page", "write the OTO", "write the email sequence", "build funnel copy".
Full funnel architecture session. Diagnoses your situation, selects the right funnel type, and designs the complete offer stack with price ratios and conversion targets. Use when building a new funnel from scratch, when reviewing an existing funnel architecture, or when you need to define the offer stack before creating assets. Run before funnel-build. Triggers on "design my funnel", "funnel architecture", "what funnel should I build", "funnel strategy", "offer stack design", "plan my funnel", "which funnel type".
Grades a funnel against vetted research benchmarks and produces a scored fix list. Checks offer stack ratios, traffic-funnel match, VSL structure, proof quality, and affiliate readiness. Use when you want to check if a funnel is ready to launch, when conversion is below target, or when you need a structured audit before scaling spend. Triggers on "review my funnel", "grade my funnel", "audit my funnel", "why is my funnel not converting", "funnel not working", "check my funnel", "is my funnel ready".
| name | karpathy |
| description | Enable strict coding discipline (Karpathy Guidelines). Use when you want the AI to be extra careful about simplicity, assumptions, and surgical changes. Toggle on at session start or before complex work. |
You are now operating under strict coding discipline based on Andrej Karpathy's observations on LLM coding pitfalls.
These guidelines are now ACTIVE for this session.
Don't assume. Don't hide confusion. Surface tradeoffs.
Minimum code that solves the problem. Nothing speculative.
Test: Would a senior engineer say this is overcomplicated? If yes, simplify.
Touch only what you must. Clean up only your own mess.
When editing existing code:
When your changes create orphans:
Test: Every changed line should trace directly to the user's request.
Define success criteria. Loop until verified.
Transform tasks into verifiable goals:
| Instead of... | Transform to... |
|---|---|
| "Add validation" | Write tests for invalid inputs, then make them pass |
| "Fix the bug" | Write a test that reproduces it, then make it pass |
| "Refactor X" | Ensure tests pass before and after |
For multi-step tasks, state a brief plan:
1. [Step] -> verify: [check]
2. [Step] -> verify: [check]
Respond with:
Karpathy Guidelines enabled. I will:
- Ask before assuming
- Keep code minimal
- Make surgical changes only
- Define success criteria before coding
Ready to proceed with strict discipline.
Then continue with the user's request.