This file is the canonical process for generating and updating package skills in this repository.
This process currently covers:
packages/vue/skills/rstore-vuepackages/nuxt/skills/rstore-nuxtpackages/nuxt-drizzle/skills/rstore-nuxt-drizzle
Always generate skill content from documentation (not source code), and never generate from memory.
If implementation behavior appears to differ from docs, fix docs first, then regenerate skills from the updated docs.
docs/guide/getting-started.mddocs/guide/learn-more.mddocs/guide/schema/collection.mddocs/guide/schema/relations.mddocs/guide/schema/federation.mddocs/guide/schema/collection-defaults.mddocs/guide/data/query.mddocs/guide/data/mutation.mddocs/guide/data/form.mddocs/guide/data/live.mddocs/guide/data/cache.mddocs/guide/data/module.mddocs/guide/data/offline.mddocs/guide/plugin/setup.mddocs/guide/plugin/hooks.md
docs/guide/getting-started.md(Nuxt section)docs/index.md(Nuxt integration overview)docs/guide/data/cache.mddocs/guide/plugin/hooks.mddocs/guide/data/query.md
docs/plugins/nuxt-drizzle.mddocs/guide/data/query.mddocs/guide/data/live.mddocs/guide/data/offline.mddocs/guide/schema/relations.mddocs/guide/plugin/hooks.md
For each package skill, generate:
SKILL.mdreferences/index.mdreferences/api-*.md(one file per API/config/hook element, linked fromreferences/index.md)
Expected paths:
packages/vue/skills/rstore-vue/SKILL.mdpackages/vue/skills/rstore-vue/references/*.mdpackages/nuxt/skills/rstore-nuxt/SKILL.mdpackages/nuxt/skills/rstore-nuxt/references/*.mdpackages/nuxt-drizzle/skills/rstore-nuxt-drizzle/SKILL.mdpackages/nuxt-drizzle/skills/rstore-nuxt-drizzle/references/*.md
Each generated SKILL.md should include:
- YAML frontmatter:
namedescription(single line, intent-first trigger text)
- Title and one-line summary.
- Documentation map table with docs URLs and/or shipped skill reference links.
- Core concepts table (API or module primitives and what they do).
- Quick-start snippet.
- Practical guidance sections:
- task/workflow guidance
- extension points
- guardrails/failure modes
- References section containing a table (
Topic,Description,Reference) that links every reference file. - Further reading section with docs URLs and/or shipped skill references (no source/test paths).
Each skill should include a references/ folder with API-reference files. Keep references one level deep from SKILL.md.
Mandatory layout:
references/index.md: map every documented API/config/hook element to exactly one file.references/api-<element>.md: one file per API/config/hook element (for exampleapi-find-first.md,api-find-many.md).
Each reference file should:
- start with a short title and one-line scope
- include a top
name/descriptiontable - include explicit sections in this order when possible:
Surface,Syntax,Behavior,Requirements,Pitfalls - include only behavior that is grounded in current docs
- focus on concrete API behavior, not broad conceptual overviews
- avoid linking to nested reference chains
- avoid bundling multiple API elements in one file
- Keep guidance practical and implementation-grounded.
- Prefer precise behavior over aspirational wording.
- Include only APIs/patterns that exist in current docs.
- Mark deprecations only when they are documented.
- Keep context lean: move deep detail to docs and skill references instead of embedding long prose.
- For wrapper skills, include explicit package-skill references:
@rstore/nuxtmust reference therstore-vueskill.@rstore/nuxt-drizzlemust reference bothrstore-nuxtandrstore-vue.
- Never use cross-package relative paths (
../) insideSKILL.md; reference other skills by skill name. - Never reference local source/test files from
SKILL.mdorreferences/*.mdfiles. - Do not generate or update
agents/openai.yamlfor this workflow.
The description field is the primary trigger signal used by AI agents. Write it for natural user intent matching, not for API catalog completeness.
- Start with the user goal/outcome (
fetch data,update records,set up integration,debug hydration) and then mention package-specific cues. - Start with explicit intent language such as
Use for ...,Use when ...,set up,fix,debug,migrate,integrate,extend. - Include both broad task phrases and concrete package cues (for example:
Nuxt module setup,SSR hydration,Drizzle filters,query/liveQuery,createForm). - Prefer user-language synonyms over only internal API names.
- Keep it on one line and avoid parenthetical API dumps.
- Keep wrapper boundaries clear:
rstore-nuxt: Nuxt module/runtime integration concerns; explicitly reference therstore-vueskill by name.rstore-nuxt-drizzle: Drizzle-backed generation/API/realtime/offline concerns; explicitly reference bothrstore-nuxtandrstore-vueby name.rstore-vue: base store/query/form/plugin/module behavior.
rg --files docs
rg -n "defineCollection|query|liveQuery|createForm|definePlugin|defineModule|rstoreDrizzle|allowTables|drizzleImport|rstoreDirs" docsRead the documentation source-of-truth files listed above. If docs are missing or contradictory, update docs first and use the updated docs as the generation input.
- Regenerate
SKILL.mdfor each package using the required structure. - Regenerate
references/index.mdandreferences/api-*.mdwith one file per API/config/hook element. - Ensure
SKILL.mdlinks toreferences/index.md.
sed -n '1,260p' packages/vue/skills/rstore-vue/SKILL.md
sed -n '1,260p' packages/nuxt/skills/rstore-nuxt/SKILL.md
sed -n '1,320p' packages/nuxt-drizzle/skills/rstore-nuxt-drizzle/SKILL.mdChecklist:
- Frontmatter is valid and trigger description is specific.
- Every major claim is backed by current docs.
- Quick-start snippets are valid for the package.
- Guardrails mention real failure modes from runtime behavior.
-
references/index.mdexists and links to allreferences/api-*.mdfiles. - Each
api-*.mdfile documents exactly one API/config/hook element. -
SKILL.mdcontains a reference table (Topic,Description,Reference) covering all skill references. -
rstore-nuxtreferences therstore-vueskill by name (no cross-package relative paths). -
rstore-nuxt-drizzlereferences bothrstore-nuxtandrstore-vueby name (no cross-package relative paths). - No source/test file paths are referenced from skill files.
After regeneration, update this document:
- Generation date
- Docs commit SHA
- Version notes (if applicable)
- What was regenerated
When documentation changes, update only impacted skills.
git diff <last_skill_sha>..HEAD -- docs
git diff --name-only <last_skill_sha>..HEAD -- docsThen:
- Map changed docs files to affected package skills.
- Update only relevant sections.
- Re-validate claims against current docs.
- Refresh metadata below.
- Last generation date: 2026-03-08
- Docs commit SHA:
4d458c9edaf98cc52884c8e8547d5b5e9884c03b - Docs short SHA:
4d458c9 - Docs commit date: 2026-03-03 01:53:55 +0100
- Docs commit message:
fix(module): module getting disposed - Generated artifacts:
packages/vue/skills/rstore-vue/SKILL.mdpackages/vue/skills/rstore-vue/references/*.mdpackages/nuxt/skills/rstore-nuxt/SKILL.mdpackages/nuxt/skills/rstore-nuxt/references/*.mdpackages/nuxt-drizzle/skills/rstore-nuxt-drizzle/SKILL.mdpackages/nuxt-drizzle/skills/rstore-nuxt-drizzle/references/*.md
- There is no dedicated generation script in this repository yet.
- Generation is currently a documented manual process with reproducible inspection commands.