fix(skill): AI skill drift — dead routing refs, phantom components (B24Slider/B24AuthForm), index.json desync, broken examples #93

Activity

1. IgorShevchik

   added

   bugSomething isn't workingSomething isn't working

   documentationImprovements or additions to documentationImprovements or additions to documentation

   on Jun 9, 2026
2. IgorShevchik

   added 2 commits that reference this issue on Aug 9, 2026

   fix(skill): close the drift the six reviewers found beyond #93's chec…

   ...

   9f767ad

   docs(porting): record that skills/ is b24ui-authored, and close two g…

   ...

   65812e9
3. IgorShevchik

   closed this as completedin #343on Aug 9, 2026
4. IgorShevchik commented on Aug 9, 2026

   

   IgorShevchik

   on Aug 9, 2026 – with Claude

   CollaboratorAuthor

   More actions

   Fixed and merged in #343 🧭

   Every box on the checklist is ticked, plus nine more of the same species that the review round flushed out of files this issue never named. Turns out when you go looking for one dead reference, you find its extended family.

   The routing table no longer sends anyone to auth, chat, docs or editor. Those four were inherited from the nuxt/ui skill and never existed here, which is a fun kind of bug: the agent dutifully tries to load a file, finds nothing, and carries on with whatever it already believed. They now point at the sections of components.md that actually cover chat, the editor and markdown. detail-panel.md and task-form.md — 500 lines of genuinely good material that no row named — are routed too, and icons finally got the row it never had.

   The phantoms are gone. B24Slider is B24Range (the links were right the whole time, only the name was wrong), UFieldGroup is B24FieldGroup, and B24AuthForm — which the skill recommended for every login page, alongside a Russian parenthetical quietly admitting there were no docs — never existed at all. Login pages now compose what does:

   <B24Form :schema="schema" :state="state" @submit="onSubmit">
     <B24FormField label="Email" name="email">
       <B24Input v-model="state.email" type="email" autocomplete="username" />
     </B24FormField>
     <B24FormField label="Password" name="password">
       <B24Input v-model="state.password" type="password" autocomplete="current-password" />
     </B24FormField>
   </B24Form>

   And the examples now run. The worst one was card-pickers.md, which imported LayoutGridIcon, LayoutListIcon and LayoutKanbanIcon from a package that has no icon named Layout anything — and, in a detail I enjoyed rather more than I should have, that file was one of the two this same PR added to index.json. It had just started shipping to agents, and it failed on first use. Also fixed: the Cyrillic И in <И24Card>, :icon="{AchievementIcon}" binding an object where a component belongs, variant="ghost" on seven buttons (there is no variant prop — the skill's own forms guideline said so, two files away), color="neutral" matching no key in the theme, an undefined PlusLIcons, and form.clearErrors() for what is actually clear().

   Special mention for Core rule 3, the single highest-traffic sentence in the package, which told every agent to read .nuxt/ui/<component>.ts. We write to .nuxt/b24ui/. The sibling design-system guideline had it right; the rule had been quietly wrong since the fork.

   The part that matters most is that none of this can come back silently. test/utils/skill-manifest.spec.ts runs ten checks in CI: component names under both registered prefixes (B24* and Prose* — an earlier draft accepted 35 names that do not exist, because prose components are registered differently), icon imports against the very metadata file the skill tells agents to search, links that must resolve inside the installed package, manifest parity in both directions, and routing checked both ways — because "listed but unreachable" is exactly how detail-panel.md got lost. Every check was mutation-tested against the defect it guards.

   Want to see it work? Try:

   Using the b24ui skill, build a settings page with a layout picker (table / list / kanban) and a login form. Follow the routing table and load only the references it names.

   Nothing in the npm package changed — skills/ is not published — so this ships as a docs entry rather than a version bump.

   Two follow-ups filed with full context: #344 (generate index.json and the components.md table from the docs frontmatter, so those two cannot drift at all) and #345 (guard prop and colour names, not just identifiers — the one gap the new checks can't see).

   Thanks from Igor 🙏

   ---

   Generated by Claude Code
5. IgorShevchik

   added 2 commits that reference this issue on Aug 10, 2026

   docs(porting): record that the manifest is generated, close two revie…

   ...

   2d4628a

   docs(skill): generate skills/index.json instead of hand-maintaining it (

   ...

   227cd4e
6. eshimischi

   added a commit that references this issue on Sep 14, 2026

   docs(skill): dead routing refs, phantom components, manifest desync, …

   ...

   This issue will close once commit 0fb88ac is merged into the 'main' branch.

   0fb88ac