01 operating system
14-category autonomous product-building OS for 32+ AI coding tools. One-line prompts → deployed products.
npx -y skills add heymegabyte/claude-skills --skill 01-operating-systemAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 18 stars18 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.
The file declares its own license as Rutgers. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
5.5 KB, as published. Nobody here has run it
01 — Operating System
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
- 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.