project-conventions

Enforce prose, code quality, token economy, and temporary file conventions for sub-agents.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/ddaanet/edify-plugin --skill project-conventions-ddaanet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-conventions
Source: https://github.com/ddaanet/edify-plugin/tree/main/skills/project-conventions
Command: npx skills add https://github.com/ddaanet/edify-plugin --skill project-conventions-ddaanet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Project prose and output conventions for sub-agents. Injected via skills: frontmatter — not user-invocable. Bundles deslop (prose quality), token economy, and tmp-directory rules.

Core Features & Use Cases

  • Code Quality: Prose quality rules have moved to ambient context (communication.md). For code:
  • Docstrings only for non-obvious behavior
  • Comments explain why, never what
  • No section banners — let structure communicate grouping
  • Abstractions only when a second use exists
  • Guard only at trust boundaries
  • Expose fields directly until access control needed
  • Build for current requirements, extend when needed
  • Token Economy:
  • Give file references (path:line), never repeat file contents
  • Use bullets unless ordering matters (numbered lists cause renumbering churn)
  • Direct, clear communication without verbosity
  • Temporary Files:
  • All temporary files go in <project-root>/tmp/, never /tmp/ or /tmp/claude/.
  • For runbook execution, use plans/*/reports/. For ad-hoc work, use project-local tmp/.

Quick Start

Adopt these conventions in new and existing skills to ensure consistent prose, outputs, and file organization.

Frequently Asked Questions about project-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce prose conventions for sub-agents in a multi-agent workflow?

You enforce prose conventions by injecting frontmatter-driven rules into sub-agents, specifying code quality, token economy, and temporary file management standards to ensure consistent outputs.

What is the standard for temporary file management in multi-agent workflows?

Temporary file management requires all temporary files to go in the project-root tmp/ directory, never /tmp/ or /tmp/claude/, using plans/*/reports/ for runbook execution.

How do I optimize token economy when sub-agents output prose?

Optimize token economy by giving file references like path:line instead of repeating file contents, using bullets unless ordering matters, and communicating directly without verbosity.

What code quality conventions should sub-agents follow for comments and docstrings?

Code quality conventions require docstrings only for non-obvious behavior, comments explaining why never what, no section banners, and abstractions only when a second use exists.

Do I need frontmatter for sub-agent skill discovery?

Frontmatter-driven discovery is required for skill units, needing a name and description, establishing a minimal operating structure for sub-agents to follow.

When should I not use numbered lists in sub-agent outputs?

Avoid numbered lists in sub-agent outputs whenever ordering does not matter, because numbered lists cause renumbering churn; use bullets instead to maintain stable prose conventions.