jlong

jlong/quiddity

Instructions file

Instructions for jlong/quiddity, covering quiddity, project structure, key concepts and writing skills.

jlong/quiddity

Skill Claude CodeCodex

Scan the current project and create a summary of its structure, important files, and conventions in .quiddity/project.md.

jlong/quiddity

Skill Claude CodeCodex

Generate a custom /approve skill for your project. Ensures your source control, CI, and PR conventions are configured via /q-which-tools, then writes a tailored skill that verifies checks and merges approved PRs.

jlong/quiddity

Skill Claude CodeCodex

Generate a custom /new-issue skill for your project. Ensures your issue tracker is configured via /q-which-tools, then writes a tailored skill that converts plain-English descriptions into well-structured issues.

jlong/quiddity

Skill Claude CodeCodex

Generate a custom /next-task skill for your project. Ensures your issue tracker, source control, and CI are configured via /q-which-tools, then writes a tailored skill that picks up the next task, implements it, and opens a PR.

jlong/quiddity

Skill Claude CodeCodex

Walk through the tools in .quiddity/tools.json and help install any missing CLIs or MCPs. Run /q-which-tools first if tools.json doesn't exist.

jlong/quiddity

Skill Claude CodeCodex

Run the full Quiddity setup flow. Discovers your process and tools, then generates custom /new-issue, /next-task, and /approve skills for your project.

jlong/quiddity

Skill Claude CodeCodex

Discover your project's software development lifecycle (SDLC) and write a process description to .quiddity/process.md. Accepts an existing document or interviews you to understand your workflow.

jlong/quiddity

Skill Claude CodeCodex

Discover what tools a project uses and save the configuration to .quiddity/tools.json. Pass category names as arguments (e.g., /q-which-tools issues source-control).