claude-code-conventions

Defines Claude Code conventions for subagent spawning, skill stubs, and document linking.

Updated Aug 25, 2026
One-click install
npx skills add https://github.com/hyvanmielenpelit/SharedAgentSkills --skill claude-code-conventions-hyvanmielenpelit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-code-conventions
Source: https://github.com/hyvanmielenpelit/SharedAgentSkills/tree/main/skills-claude/claude-code-conventions
Command: npx skills add https://github.com/hyvanmielenpelit/SharedAgentSkills --skill claude-code-conventions-hyvanmielenpelit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Working in Claude Code involves harness-specific rules that are easy to get wrong: picking a model tier for a subagent, knowing that Claude Code cannot spawn another vendor's models, keeping .claude/skills pointer stubs in sync with canonical skill bodies, and reporting planning documents as clickable links instead of dead relative paths. This Skill consolidates those conventions so agents behave correctly before spawning subagents, wiring skills, or reporting documents. ## Core Features & Use Cases - Model Tier Resolution: Maps abstract tiers (deep, standard, mechanical, inherit) to the models the current session actually offers, independent of any written table. - Spawn Boundary and Agent Types: Clarifies that Claude Code spawns only Claude models, and distinguishes the Explore, Plan, and general-purpose agent types from model tiers. - Pointer-Stub Contract: Explains the .claude/skills/<kebab-name> stub requirement and regenerating stubs with sync_stubs.ps1 so skills trigger on current descriptions. - Clickable Document Links: Specifies absolute forward-slash hrefs for plans-repository documents, when relative links are valid, and when to use SendUserFile instead of the Artifact tool. - Use Case: Before spawning a subagent to execute an approved plan, resolve the plan's tier to a session model, choose the general-purpose agent type, and report the resulting plan as an absolute-path Markdown link. ## Quick Start Read this skill before spawning a subagent, adding a skill to a project repository, or reporting a plan document in Claude Code.

Frequently Asked Questions about claude-code-conventions

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

FAQPage Schema
How do I choose a model for a Claude Code subagent?

Resolve the abstract tier (deep, standard, mechanical, or inherit) against the models the current session actually offers, not a written table. Use inherit by omitting the model override so the subagent matches the orchestrator.

Can Claude Code spawn subagents using other vendors' models?

No. Claude Code can spawn only Claude models and has no access to another vendor's models. A plan targeting another application is handed over by a person opening that application, with the plan document as the interface.

What is the difference between agent type and model tier in Claude Code?

Type and tier are independent axes. The tier is how capable the subagent is; the type is what it may do. Explore and Plan are read-only, while general-purpose can edit files for execution work.

Why is my Claude Code skill not triggering in a project repository?

The canonical skill in .agents/skills needs a matching pointer stub at .claude/skills/<kebab-name>/SKILL.md, and the stub's description is what Claude Code indexes. Regenerate stubs with sync_stubs.ps1 instead of hand-editing them.

How do I link a plan document so it opens in Claude Code?

Use a Markdown link with the absolute path written in forward slashes, since plans live outside the working repository and backslashes are treated as escape characters. Print the plain-text absolute path alongside the link.