miscsubjects

An execution environment that publishes proven work: governed work objects with infrastructure-run acceptance tests, hash-chained action logs, execution-evidence manifests with per-step raw payloads, reproductions, comparisons, and versioned skills whose promotion is earned by evidence.

Skills

• coding-law
  Use before the first edit of any file under functions/, scripts/, migrations/, workers/, apps-script/, .claude/skills/, .agents/skills/, schema.sql or wrangler.toml — and again immediately before every git commit. Take a hash when work starts, submit a hash when work commits. Prevents two agents from silently overwriting each other with individually valid commits.
  code discipline
• dispatching-parallel-agents
  Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
  code discipline
• executing-plans
  Use when you have a written implementation plan to execute in a separate session with review checkpoints
  code discipline
• finishing-a-development-branch
  Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
  code discipline
• grill-me
  A relentless interview to sharpen a plan or design.
  code discipline
• receiving-code-review
  Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
  code discipline
• requesting-code-review
  Use when completing tasks, implementing major features, or before merging to verify work meets requirements
  code discipline
• systematic-debugging
  Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
  code discipline
• test-driven-development
  Use when implementing any feature or bugfix, before writing implementation code
  code discipline
• verification-before-completion
  Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
  code discipline
• webapp-testing
  Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
  code discipline
• writing-plans
  Use when you have a spec or requirements for a multi-step task, before touching code
  code discipline
• seo-distribution-law
  Use when writing, reviewing, or shipping anything that affects how this site is found, indexed, shared, or syndicated — SEO heads, sitemaps, feeds, share surfaces, network posting, or the self-score. The site's perception of search and distribution best practices lives here, is enforced live at /api/seo/score, and is open to critique; never assert a practice from memory when this file and that endpoint disagree.
  distribution
• agent-work-law
  Use at the start of every session operating miscsubjects.com, and whenever deciding what to work on, whether work is finished, or what to do about a failure. The infrastructure is the authority; this skill tells you where it lives and how to obey it.
  the loop
• article-editing
  Use when creating, editing, sourcing, illustrating, exporting, or deleting any article on miscsubjects.com — from the admin studio, curl, a coding agent, a Cloudflare Gateway model, or Google Sheets. One REST contract for all of them.
  the loop
• self-promotion
  The build's standing procedure for promoting itself — deciding whether, whom, when, on which channel, and with which artifact to make contact whenever something ships or a reply lands. Governs the allocation, not the copy (outreach-law governs the copy). Load whenever a new article, capability, receipt, resolved defect, or inbound reply changes what the build has to show someone, or when planning any post, email, or paid spend about the build itself.
  the loop
• shared-failure-to-skill
  Use when the owner reports a recurring failure, repeated fix, or systemic issue. Convert the failure into a skill and a mechanical gate so it stops repeating.
  the loop
• shared-no-new-problems
  Use when the owner asks for a fix or reports a failure. Fix it without asking permission and without creating new problems.
  the loop
• shared-rule-capture
  Use when the owner restates a rule, correction, or constraint, or when a governor report shows high owner-restatement counts.
  the loop
• shared-say-no
  Use ONLY when answering an evaluative question — "anything to add", "any ideas", "anything wrong", "is this good/A+", a review, an audit, or a decision about whether something can be deleted. NEVER use it to answer a work instruction. Absorbed into thinking-law (owner order, 2026-08-06) as the restraint family — load thinking-law for the full verdict rules.
  the loop
• skill-creator
  Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
  the loop
• writing-skills
  Use when creating new skills, editing existing skills, or verifying skills work before deployment
  the loop

How to call

https://miscsubjects.com/api/dispatch

Listed in

Directories this entry was found in.