Keep essential conventions in view
Some conventions matter before an agent chooses a detailed guide. A database change, for example, should bring its migration obligation into view while the change is being planned.
Wildo delivers standing rules alongside its skills and connects them to the application’s guidance file. Your project’s own instructions stay outside the managed block.
Example — Remember the migration with the schema change
An agent adds a stored field to a PostgreSQL-backed resource. The standing guidance directs attention to the migration as part of that change, rather than leaving it until the application meets the database.
For engineers
Files and imports are separate parts of delivery
wildo assets sync delivers the package’s guidance into the application. Rules live under .claude/rules/; the installer also maintains their imports in CLAUDE.md.
This representative generated block uses the current rule filenames:
<!-- BEGIN WILDO MANAGED RULE IMPORTS -->
@.claude/rules/database-migration-obligation.md
@.claude/rules/live-context-door.md
@.claude/rules/resource-schema-awareness.md
<!-- END WILDO MANAGED RULE IMPORTS -->
The imports are sorted. An existing managed block is replaced; otherwise the block is appended to the existing guidance file. Instructions outside those markers remain application-owned. An existing guidance file is needed for that import entry point; inspect it explicitly after synchronization.
Choose standing guidance deliberately
| Put in standing guidance | Put in a task-specific skill |
|---|---|
| Conventions relevant across ordinary development | A detailed workflow for one kind of change |
| The need to consult application context | Reference material needed only for that task |
| Obligations that should be noticed early | Longer examples and specialized configuration choices |
The host must read the guidance file and support its import convention. Installed instructions help an agent reason; they are not a runtime permission check or a guarantee that every model will follow them.
Verify the delivered connection
After synchronization, inspect both the rule files and the managed block. The skill-file publication and subsequent guidance-file update are separate operations. Inspect CLAUDE.md for the managed imports as well as checking the installed rule files. Do not infer successful host loading from the existence of a rule file alone.