skills.rest
julien-m
julien-mCOMMUNITY
Explore all skills by this author →
GitHub

spec-refresh-conventions

Regenerates the project conventions bundle from the LiveSpec stack definition.

Updated Mar 11, 2026
Search Tags:#migration#conventions#manifest#stack#regenerate#dry-run#livespec
One-click install
npx skills add https://github.com/julien-m/livespec --skill spec-refresh-conventions-julien-m
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-refresh-conventions
Source: https://github.com/julien-m/livespec/tree/main/.agent-sync/skills/spec-refresh-conventions
Command: npx skills add https://github.com/julien-m/livespec --skill spec-refresh-conventions-julien-m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project conventions can become stale or missing after stack changes, failed initialization hooks, or legacy format migrations, leaving AI assistants without accurate coding guidance. ## Core Features & Use Cases - Conventions Bundle Rebuild: Regenerates .conventions/index.md and .conventions/manifest.yaml from the stack defined in .specs/stacks/_default.md. - Legacy Migration: Detects and removes the legacy compiled .conventions/conventions.md format, migrating to the new index plus manifest layout. - Signal Extraction: Reads stack and project files to extract technology signals (e.g., typescript, bun, react) that drive sub-domain detection. - Use Case: After switching your project from Node to Bun, run this command to rebuild the conventions bundle so all subsequent LiveSpec commands load conventions matching the new stack. ## Quick Start Ask the AI to run /spec-refresh-conventions to rebuild the project conventions bundle from the current LiveSpec stack. Supports --full (default rebuild), --force (alias), and --dry-run (report only, no writes).

Frequently Asked Questions about spec-refresh-conventions

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

FAQPage Schema
How do I regenerate project conventions in LiveSpec?▼

Run /spec-refresh-conventions to rebuild the conventions bundle from your stack file. It reads .specs/stacks/_default.md, extracts technology signals, and writes .conventions/index.md and .conventions/manifest.yaml via the bootstrap path.

How do I migrate from legacy conventions.md to the new format?▼

Run /spec-refresh-conventions and it automatically detects the legacy compiled .conventions/conventions.md file, deletes it, and generates the new index.md plus manifest.yaml layout in its place.

What happens if no stack file exists when refreshing conventions?▼

The command skips generation cleanly and reports a NO STACK status, instructing you to run /spec-init first to define a stack. It does not produce an error or partial output.

Can I preview convention changes without writing files?▼

Yes, pass the --dry-run or -d flag. The command runs the guard, legacy detection, and signal extraction steps and displays the full report, but does not invoke the refresh or delete any legacy file.

Why does conventions refresh fail with an ai-ressources error?▼

The refresh depends on the ai-ressources repository for domain catalog resolution. If the path is wrong, set the $AIRESOURCES environment variable to the correct location and retry the command.

Related Skills

Explore More Software Engineering Skills→
astrovilleastroville

greenfield-scaffolding

Generate starter conventions, decisions, and specs for a new Hero workspace based on the detected tech stack.

Official
Intermediate
inspedralbesinspedralbes

speckit-plan

Generate design artifacts from a plan template for spec-kit projects.

Official
Advanced
PeterFilePeterFile
4

living-documentation

Sync .kiro/specs requirements and design docs with code changes.

Community
Basic
thewoolleymanthewoolleyman

livespec-help

Explains livespec capabilities and routes users to the correct livespec operation.

Community
Intermediate