Design and optimize function/method parameter lists when defining or refactoring API interfaces, method signatures, or function parameters. Apply best practices for parameter count, ordering, pass mechanisms, and documentation to create clear, efficient, and maintainable interfaces.
Use this skill when writing, reviewing, or refactoring code to ensure it is self-documenting. Apply these checklists to routines, data naming, data organization, and overall code layout to improve code clarity and maintainability without relying on comments.
Apply self-documenting code practices through good programming style and evaluate class design for abstraction quality. Use when writing code, conducting code reviews, designing class interfaces, or establishing documentation standards.
Use this skill when you need to reference, cite, or apply software engineering standards. This skill provides the IEEE/ISO standard naming convention and categorized lists of standards for software development, quality assurance, and project management.
Reference and apply IEEE, ISO/IEC, and other software engineering standards for development, quality assurance, and project management. Use when selecting standards for specific activities, formatting standard references, establishing project frameworks, or creating documentation templates.
Access and study real-world production code examples from SourceForge. Use this skill when you need to see larger, practical code examples beyond textbook snippets, especially for learning good and bad coding practices in various programming languages.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
John — a Claude Code and Codex harness for building knowledge-dense apps. Wraps the agent with skills, hooks, commands, and a small toolkit so it can take unstructured input through knowledge phases (knowledge engineering) and app phases (app building) in one long-running session; includes a deterministic…
Use this agent during the app phases when produced-app code needs an independent quality review — an opt-in cross-validation pass per the code-quality-guardrails skill. Reviews a specified set of files against the four guardrail categories (security, quality, UX, deployment), runs whatever deterministic checks the…
Use this agent in the adversarial cross-check stage of a fan-out phase to re-read ONE source chunk independently and find knowledge entries the extractor MISSED (MECE enforcement). It does not re-extract or rewrite — it audits coverage and emits coveragegap events. Dispatch one per chunk (or per sampled chunk) in a…
Use this agent in the adversarial cross-check stage of a fan-out phase to verify that every extracted entry from ONE chunk traces to actual source text — and flag the ones that don't, so ungrounded (hallucinated or over-inferred) entries are filtered before they fold into canonical state. Emits groundingflag events.…
Use this agent to extract knowledge entries from a single source chunk during the knowledge-phase extraction step. Each invocation processes ONE chunk and emits structured entries (facts, rules, slide-concepts, etc. — whatever the project's schema dictates) as JSON events to /.john/events/extract/ /. Designed for…
Use this agent during the schema-design phase when a project's knowledge schema needs multi-turn iteration on a representative sample of source material — the schema-pilot step. Reads N chunks (3–10 is typical), proposes a schema shape, tests it mentally against the chunks, refines, and returns a settled schema with…
Bundle the finished John workspace (PLAN.md, CLAUDE.md, AGENTS.md, .john/, .claude/skills/, .agents/skills/) into a release zip. Use when the user says "archive this project", "package it up", "we're done", or you've completed an end-to-end run and want a portable bundle. Excludes git/pycache/nodemodules cruft.
Set or clear the long-running goal for this John session. Pinned into the system prompt by the SessionStart hook so it survives context compaction and stays visible across long ralph-loop runs. Use this command when the user says "let's run this in endurance mode", "set the endurance goal to ...", "/john:endurance…
Scaffold the John workspace in the current project. Creates .john/ working state, a starter PLAN.md, and (if missing) a starter CLAUDE.md. Optionally copies an input path into .john/input/. ALWAYS run this first when starting a new John project — every other John command depends on .john/ existing.
Assemble a run report — the shareable postmortem of this John run (process scorecard + manifest + outcome summary + candidate lessons), privacy-scrubbed. Use when a run wraps or a milestone ships, when the user asks "how did this run go?", "make a run report", or wants evidence to send a template owner. The report is…
Print John workspace status — active template, current phase, inventory of inputs/parsed/chunks/knowledge/events/checkpoints/produced-skills. Use whenever the user asks "where are we?", "what's done?", "what's next?", or you need to verify state before advancing a phase. Cheap; run it generously.
Runs after a tool call finishes for Read, Bash, Write, Edit and Skill tool calls, executing post_tool_use_hook.py and skill_invocation_hook.py via python3 (2 commands). From kitchen-engineer42/joharnessburg.
Design the app mechanism and build pipeline for the produced app — the app-phase analog of [[schema-design]]. Use this skill whenever the knowledge phases are complete (or nearly so), when the user mentions building the app / runtime / UX / production / deploy, when the app-type definition section of PLAN.md needs its…