Menu
Quick-reference summary of project conventions for fast agent consumption
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Install ComfyUI Assistant as a ComfyUI custom node. Use when performing or troubleshooting installation (clone, Python deps, frontend build, restart).
For complex user requests — evaluate, investigate, ask questions, propose a plan, accept modifications, then execute. Use when the request is multi-step, ambiguous, or high-impact.
Workflow execution and complete workflow generation tools (executeWorkflow, applyWorkflowJson). Use when the user wants to run a workflow or build a complete workflow from a description.
Python backend modules, chat request lifecycle, SSE format, and API endpoints
System prompt assembly from system_context, user_context, and environment sources
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
| name | patterns-and-conventions |
| description | Quick-reference summary of project conventions for fast agent consumption |
| version | 0.0.1 |
| license | MIT |
Quick-reference of .agents/conventions.md. Read the full file for details; this skill covers the essentials.
eval() or dynamic code execution -- ever.env files| Rule | Value |
|---|---|
| Quotes | Single |
| Semicolons | None |
| Indentation | 2 spaces |
| Line width | 80 chars |
| Trailing commas | None |
| Types | Strict mode, no any, use unknown |
| Schemas | Zod for runtime validation, z.infer<> for types |
| Errors | Return { success, data?, error? } -- never throw |
| Imports | core -> third-party -> local |
| Components | Named exports, typed Props interface |
| Rule | Value |
|---|---|
| Indentation | 4 spaces |
| Naming | snake_case functions/vars, PascalCase classes |
| Type hints | Required on all signatures |
| Docstrings | Required on all public functions |
| Error handling | Try/except with structured returns |
| Imports | stdlib -> third-party -> local |
type(scope): description
feat, fix, docs, refactor, test, chore, securityfeature/add-widget-tool, fix/memory-leak-in-stream| Directory | Purpose | Examples |
|---|---|---|
.project/planning/ | Ideas, roadmaps, specs, WIP | Feature proposals, phase plans |
.project/development/ | Phase implementation records | phase_1/implemented.md |
.agents/ | Agent skills and project docs | Skills, conventions, project context |
doc/ | User and developer documentation | Install guide, tools reference |
Golden rule: If code changes, documentation changes -- same PR.
Read the "Documentation Maintenance Protocol" in .agents/conventions.md section 7. It has a checklist per change type (architecture, patterns, features).
Always under .project/planning/. Never at the repo root.
Under .project/development/<phase_name>/implemented.md.