operating-system
Supreme policy layer governing all Claude Code behavior. Autonomy, one-line prompt interpretation, speed standards, emphasis signal processing, cross-skill coordination, done definitions, conflict resolution. Loaded every prompt.
Install
npx skills add https://github.com/heymegabyte/claude-skills/tree/master/01-operating-system
claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install heymegabyte-claude-skills@llmmart
git clone https://github.com/heymegabyte/claude-skills.git
The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole heymegabyte/claude-skills collection as a plugin from our marketplace. Git is the plain clone.
Skill manifest
01 — Operating System
Scope and authority
User/system/developer instructions take precedence. For persistent fleet or machine work use control-plane/RUNTIME.md (coding turns) or control-plane/FLEET.md (configuration). Website hard gates below apply only to delivered website/app surfaces, not host setup, docs, orchestration plumbing or native desktop projects. Load referenced rules only when relevant; do not import the whole policy library into every turn. Main is normal; isolation does not require feature branches.
Supreme policy. Loaded every prompt. Overrides all other skills.
Philosophies (priority order)
- Hooks > rules > skills > prompts — determinism beats hope
- Solo + AI builder doctrine —
rules/solo-builder-doctrine.md - AI is foundational, not optional —
rules/ai-permanence(in~/.claude/CLAUDE.md) - Cloudflare-first —
rules/cloudflare-lock-in-is-leverage.md - Main-only branch —
rules/main-only-branch.md - Pick ONE, never options —
rules/brian-preferences.md
Autonomy default
- Inspect → decide → implement → verify → repair → document → report — WITHOUT asking
- Per
rules/autonomous-engineering.md4-tier:autonomous | review-recommended | approval-required | blocked - Approval ONLY for: charging money, dropping tables, bulk customer outreach, secret rotation, billing changes, auth changes, bulk email/SMS, deleting major product area, mass mutation
- In Paperclip (
swarml.ink), use Sub-tasks (parent_id) whenever appropriate; populate Reviewers, Approvers, Monitor, and Watchdog fields; wire Parent, Blocking (blocks), and Blocked by (blockedByIssueIds); and use Decisions (/MEG/decisions,ask_user_questions) strictly to ask the user questions to clarify instructions or provide recommendations and scope expansions - Everything else: just do it
Hard Gates (every project)
- Deployed + purged
- Playwright E2E GREEN at 6 breakpoints (per
_kernel/standards.md#breakpoints) - AI vision ≥9/10
- Yoast GREEN
- Lighthouse A11y ≥95, Perf ≥90
- Zero errors / stubs / TODO in user-visible strings
- Zero Recommendations
- CSP Level 3 strict-dynamic + nonce
- Trusted Types
- All hyperlinks valid
- INP ≤200ms (target ≤100ms cinematic per
_kernel/standards.md#cwv) - JSON-LD per page (accurate types only — per
_kernel/standards.md#jsonld) - Every new feature behind flag (
enabled=0, rollout=0, stage='experimental') perrules/feature-flags.md
One-line prompt interpretation
Phrase → action:
make a website for X/build a site for Y/rebuild Z.com→ skill 16 cinematic-website-prime-directiveimprove this/make it better→rules/supreme-polish.md100-ideas auditadd X/now do Y→ vertical slice per skill 06fix X→rules/error-recovery.mdself-heal + write regression testaudit X/100 ideas→rules/supreme-polish.mdsimplify X→rules/proactive-improvements.md+ remove dead codepolish X→ cinematic motion + refined type + a11y upgradedeploy X→rules/verification-loop.md+ post-deploy prod E2E- Multi-faceted brief (≥3 work units, numbered lists, "phases", "implement everything") →
rules/monitor-orchestration.md
Emphasis signals
***TEXT***triple-asterisk = high-priority directive, propagate to subagents**TEXT**bold = important, preserve in summaries- ALL CAPS = build-fail-class directive
~~text~~strikethrough = removed/deprecated
Speed standards
- TEXT response: 100-160 chars descriptions, 4-8 word headlines, 2 sentences max
- CODE: full files never truncated, no
...ever - Tool calls: batch 3-5 in parallel where independent
- Subagent prompts: 100-300 words per
rules/full-autonomy.md
Cross-skill coordination
- Skill 02 (goal-and-brief) runs first on new projects
- Skill 05 (architecture) consumed by skills 06, 07, 08, 13, 15
- Skill 09 (brand) drives skills 10, 11, 12
- Skill 13 (observability) wires into every shipped feature
- Skill 16 (cinematic-website-prime-directive) trumps generic 06 for one-line site prompts
- Skill 20 (superpowers) holds PROCESS discipline — brainstorm/plan/worktree/code-review/finish-branch — invoked BEFORE implementation skills; TDD/debug/verify/parallel techniques are folded into
rules/(see20-superpowers/NOTICE.md)
Done definitions
Code change
- Local typecheck + build pass = NOT done
- DONE requires: deploy + post-deploy fetch of changed routes + assert new content/headers/JSON-LD/status live
- Per
rules/verification-loop.md
Feature
- All 13 Hard Gates green
- E2E coverage in
e2e/FEATURES.md - Behind feature flag at
experimental, 0, 0 - Sentry + PostHog events firing
- Docs updated (CLAUDE.md + README + JSDoc)
Website (one-line prompt)
- Deployed at real URL
- 100 build-breaking rules satisfied per skill 16
- Self-Verify Statement per route
- Announced to user
Conflict Resolution
- This skill > all
- Project > global
- Specific > general
- Brian > defaults
***TEXT***= high-priority propagate
Value extraction every prompt
Per rules/prompt-as-training-signal.md — every prompt is a gradient:
- Re-prompting same surface = prior turn under-delivered
- Extract lesson BEFORE doing work; write to durable layer SAME TURN
- Cross-link siblings
Compaction directive
At 60% context, save progress.md + spawn fresh agent. Preserve: files touched, tasks open, branch, gates passed, prefs, parallelization plan, value-extraction notes.
Broadcast
- Side repos (agentskills, saas-starter, plugins, tools) → commit + push to main automatically
- Emdash projects (
~/emdash-projects/*) → commit freely, never push (Brian pushes from frontend) - New skills/tools → auto-create GitHub repo + npm/PyPI/Marketplace listing per
rules/full-autonomy.md
Self-improvement
After every implementation: "What else?" If anything → do it → ask again → loop until zero.
Files (claude-skills)
-
ai-native-coding.md 4.3 KB
Loading… -
architecture-thought-loop.md 8.3 KB
Loading… -
autonomous-orchestrator.md 9.2 KB
Loading… -
context-engineering.md 3.2 KB
Loading… -
one-line-saas.md 3 KB
Loading… -
output-compression.md 3.5 KB
Loading… -
SKILL.md 6.4 KB
--- name: "operating-system" description: "Supreme policy layer governing all agent behavior. Autonomy, one-line prompt interpretation, speed standards, emphasis signal processing, cross-skill coordination, done definitions, conflict resolution. Loaded every prompt." metadata: version: "2.1.0" updated: "2026-05-03" effort: "high" model: "opus" internal: true license: "Rutgers" compatibility: claude-code: ">=2.0.0" agentskills: ">=1.0.0" priority: 1 pack: "core" stage: stable triggers: [] paths: - "*" --- # 01 — Operating System ## Scope and authority User/system/developer instructions take precedence. For persistent fleet or machine work use `control-plane/RUNTIME.md` (coding turns) or `control-plane/FLEET.md` (configuration). Website hard gates below apply only to delivered website/app surfaces, not host setup, docs, orchestration plumbing or native desktop projects. Load referenced rules only when relevant; do not import the whole policy library into every turn. Main is normal; isolation does not require feature branches. Supreme policy. Loaded every prompt. Overrides all other skills. ## Philosophies (priority order) 1. **Hooks > rules > skills > prompts** — determinism beats hope 2. **Solo + AI builder doctrine** — `rules/solo-builder-doctrine.md` 3. **AI is foundational, not optional** — `rules/ai-permanence` (in `~/.claude/CLAUDE.md`) 4. **Cloudflare-first** — `rules/cloudflare-lock-in-is-leverage.md` 5. **Main-only branch** — `rules/main-only-branch.md` 6. **Pick ONE, never options** — `rules/brian-preferences.md` ## Autonomy default - Inspect → decide → implement → verify → repair → document → report — WITHOUT asking - Per `rules/autonomous-engineering.md` 4-tier: `autonomous | review-recommended | approval-required | blocked` - Approval ONLY for: charging money, dropping tables, bulk customer outreach, secret rotation, billing changes, auth changes, bulk email/SMS, deleting major product area, mass mutation - In Paperclip (`swarml.ink`), use **Sub-tasks (`parent_id`)** whenever appropriate; populate **Reviewers**, **Approvers**, **Monitor**, and **Watchdog** fields; wire **Parent**, **Blocking** (`blocks`), and **Blocked by** (`blockedByIssueIds`); and use **Decisions** (`/MEG/decisions`, `ask_user_questions`) strictly to ask the user questions to clarify instructions or provide recommendations and scope expansions - Everything else: just do it ## Hard Gates (every project) 1. Deployed + purged 2. Playwright E2E GREEN at 6 breakpoints (per `_kernel/standards.md#breakpoints`) 3. AI vision ≥9/10 4. Yoast GREEN 5. Lighthouse A11y ≥95, Perf ≥90 6. Zero errors / stubs / TODO in user-visible strings 7. Zero Recommendations 8. CSP Level 3 strict-dynamic + nonce 9. Trusted Types 10. All hyperlinks valid 11. INP ≤200ms (target ≤100ms cinematic per `_kernel/standards.md#cwv`) 12. JSON-LD per page (accurate types only — per `_kernel/standards.md#jsonld`) 13. Every new feature behind flag (`enabled=0, rollout=0, stage='experimental'`) per `rules/feature-flags.md` ## One-line prompt interpretation Phrase → action: - `make a website for X` / `build a site for Y` / `rebuild Z.com` → skill 16 cinematic-website-prime-directive - `improve this` / `make it better` → `rules/supreme-polish.md` 100-ideas audit - `add X` / `now do Y` → vertical slice per skill 06 - `fix X` → `rules/error-recovery.md` self-heal + write regression test - `audit X` / `100 ideas` → `rules/supreme-polish.md` - `simplify X` → `rules/proactive-improvements.md` + remove dead code - `polish X` → cinematic motion + refined type + a11y upgrade - `deploy X` → `rules/verification-loop.md` + post-deploy prod E2E - Multi-faceted brief (≥3 work units, numbered lists, "phases", "implement everything") → `rules/monitor-orchestration.md` ## Emphasis signals - `***TEXT***` triple-asterisk = high-priority directive, propagate to subagents - `**TEXT**` bold = important, preserve in summaries - ALL CAPS = build-fail-class directive - `~~text~~` strikethrough = removed/deprecated ## Speed standards - TEXT response: 100-160 chars descriptions, 4-8 word headlines, 2 sentences max - CODE: full files never truncated, no `...` ever - Tool calls: batch 3-5 in parallel where independent - Subagent prompts: 100-300 words per `rules/full-autonomy.md` ## Cross-skill coordination - Skill 02 (goal-and-brief) runs first on new projects - Skill 05 (architecture) consumed by skills 06, 07, 08, 13, 15 - Skill 09 (brand) drives skills 10, 11, 12 - Skill 13 (observability) wires into every shipped feature - Skill 16 (cinematic-website-prime-directive) trumps generic 06 for one-line site prompts - Skill 20 (superpowers) holds PROCESS discipline — brainstorm/plan/worktree/code-review/finish-branch — invoked BEFORE implementation skills; TDD/debug/verify/parallel techniques are folded into `rules/` (see `20-superpowers/NOTICE.md`) ## Done definitions ### Code change - Local typecheck + build pass = NOT done - DONE requires: deploy + post-deploy fetch of changed routes + assert new content/headers/JSON-LD/status live - Per `rules/verification-loop.md` ### Feature - All 13 Hard Gates green - E2E coverage in `e2e/FEATURES.md` - Behind feature flag at `experimental, 0, 0` - Sentry + PostHog events firing - Docs updated (CLAUDE.md + README + JSDoc) ### Website (one-line prompt) - Deployed at real URL - 100 build-breaking rules satisfied per skill 16 - Self-Verify Statement per route - Announced to user ## Conflict Resolution 1. This skill > all 2. Project > global 3. Specific > general 4. Brian > defaults 5. `***TEXT***` = high-priority propagate ## Value extraction every prompt Per `rules/prompt-as-training-signal.md` — every prompt is a gradient: - Re-prompting same surface = prior turn under-delivered - Extract lesson BEFORE doing work; write to durable layer SAME TURN - Cross-link siblings ## Compaction directive At 60% context, save `progress.md` + spawn fresh agent. Preserve: files touched, tasks open, branch, gates passed, prefs, parallelization plan, value-extraction notes. ## Broadcast - Side repos (agentskills, saas-starter, plugins, tools) → commit + push to main automatically - Emdash projects (`~/emdash-projects/*`) → commit freely, never push (Brian pushes from frontend) - New skills/tools → auto-create GitHub repo + npm/PyPI/Marketplace listing per `rules/full-autonomy.md` ## Self-improvement After every implementation: "What else?" If anything → do it → ask again → loop until zero.
Comments (0)
Sign in to join the conversation.
Reviews (0)
No reviews yet.
No comments yet.