fix: stop leaking a task number into site copy, ignore legacy sources
Two unrelated cleanups from the 14-17 wave.
The review desk footer told visitors to mirror entries into catalog.js
'until task 16 rewires the page to read the collection'. Introduced by
b484302 (task 06), it shipped in the built HTML. The mirroring advice is
still correct -- verify.mjs:24,52,54 confirm the desk reads catalog.js --
so only the internal task reference is dropped.
.prettierignore now covers the legacy sources. They have very long lines,
so lint-staged re-wraps them wholesale as soon as an agent stages one:
task 15 added four lines to app.js and produced an 829-line diff. Paths
are root-anchored so a bare 'rules' does not swallow .agents/rules/.
This commit is contained in:
@@ -45,7 +45,7 @@ submitted-skills/
|
|||||||
src/content/reviews/{new-id}.md
|
src/content/reviews/{new-id}.md
|
||||||
(and mirror it into
|
(and mirror it into
|
||||||
skills-review/catalog.js
|
skills-review/catalog.js
|
||||||
until task 16 rewires the page to read the collection), then run
|
which the desk still reads), then run
|
||||||
node scripts/build-skill-review.mjs
|
node scripts/build-skill-review.mjs
|
||||||
. Votes call a separate service — see
|
. Votes call a separate service — see
|
||||||
vote-service/
|
vote-service/
|
||||||
|
|||||||
@@ -7,3 +7,23 @@ skill-reviews
|
|||||||
vote-service
|
vote-service
|
||||||
.agents/snapshots
|
.agents/snapshots
|
||||||
pnpm-lock.yaml
|
pnpm-lock.yaml
|
||||||
|
public/submitted-skills
|
||||||
|
|
||||||
|
# Legacy site sources, slated for deletion at cutover (task 20). These are
|
||||||
|
# hand-written files with very long lines; prettier re-wraps them into hundreds
|
||||||
|
# of changed lines the moment any agent stages one. Task 15 touched app.js to
|
||||||
|
# add four lines and produced an 829-line diff. verify.mjs asserts substrings
|
||||||
|
# against several of these, so a reformat is churn at best and a broken
|
||||||
|
# assertion at worst.
|
||||||
|
#
|
||||||
|
# Root-anchored on purpose: a bare `rules` would also swallow .agents/rules/,
|
||||||
|
# whose markdown we do want formatted.
|
||||||
|
/app.js
|
||||||
|
/styles.css
|
||||||
|
/landing.css
|
||||||
|
/chapters.css
|
||||||
|
/responsive.css
|
||||||
|
/skills-review/
|
||||||
|
/rules/
|
||||||
|
/skills/
|
||||||
|
/full-guide/
|
||||||
|
|||||||
@@ -38,7 +38,7 @@
|
|||||||
<p>The recommendations follow the open Agent Skills format: valid frontmatter for discovery, progressive disclosure for context economy, deterministic scripts for fragile repeated mechanics, and behavioral evaluation rather than a checklist of pretty headings.</p>
|
<p>The recommendations follow the open Agent Skills format: valid frontmatter for discovery, progressive disclosure for context economy, deterministic scripts for fragile repeated mechanics, and behavioral evaluation rather than a checklist of pretty headings.</p>
|
||||||
<div><a href="https://agentskills.io/specification" target="_blank" rel="noreferrer">Format specification ↗</a><a href="https://agentskills.io/skill-creation/best-practices" target="_blank" rel="noreferrer">Writing practices ↗</a><a href="https://agentskills.io/skill-creation/evaluating-skills" target="_blank" rel="noreferrer">Evaluation loop ↗</a><a href="https://agentskills.io/skill-creation/using-scripts" target="_blank" rel="noreferrer">Scripts guide ↗</a></div>
|
<div><a href="https://agentskills.io/specification" target="_blank" rel="noreferrer">Format specification ↗</a><a href="https://agentskills.io/skill-creation/best-practices" target="_blank" rel="noreferrer">Writing practices ↗</a><a href="https://agentskills.io/skill-creation/evaluating-skills" target="_blank" rel="noreferrer">Evaluation loop ↗</a><a href="https://agentskills.io/skill-creation/using-scripts" target="_blank" rel="noreferrer">Scripts guide ↗</a></div>
|
||||||
</section>
|
</section>
|
||||||
<footer>Share an author with <code>?author=Name</code>, or one review with <code>?author=Name&skill=skill-id&view=improved</code>. To add a submission later: drop a package under <code>submitted-skills/</code>, add an entry under <code>src/content/reviews/{new-id}.md</code> (and mirror it into <code>skills-review/catalog.js</code> until task 16 rewires the page to read the collection), then run <code>node scripts/build-skill-review.mjs</code>. Votes call a separate service — see <code>vote-service/</code> — one per visitor, tracked by network source.</footer>
|
<footer>Share an author with <code>?author=Name</code>, or one review with <code>?author=Name&skill=skill-id&view=improved</code>. To add a submission later: drop a package under <code>submitted-skills/</code>, add an entry under <code>src/content/reviews/{new-id}.md</code> (and mirror it into <code>skills-review/catalog.js</code> which the desk still reads), then run <code>node scripts/build-skill-review.mjs</code>. Votes call a separate service — see <code>vote-service/</code> — one per visitor, tracked by network source.</footer>
|
||||||
</main>
|
</main>
|
||||||
<script type="module" src="app.js?v=20260904-vote-widget"></script>
|
<script type="module" src="app.js?v=20260904-vote-widget"></script>
|
||||||
</body>
|
</body>
|
||||||
|
|||||||
@@ -142,10 +142,9 @@ const serializedCatalog = JSON.stringify(catalog).replace(/</g, '\\u003c');
|
|||||||
>. To add a submission later: drop a package under <code>submitted-skills/</code>, add an
|
>. To add a submission later: drop a package under <code>submitted-skills/</code>, add an
|
||||||
entry under <code>src/content/reviews/{'{'}new-id{'}'}.md</code> (and mirror it into <code
|
entry under <code>src/content/reviews/{'{'}new-id{'}'}.md</code> (and mirror it into <code
|
||||||
>skills-review/catalog.js</code
|
>skills-review/catalog.js</code
|
||||||
> until task 16 rewires the page to read the collection), then run <code
|
> which the desk still reads), then run <code>node scripts/build-skill-review.mjs</code>.
|
||||||
>node scripts/build-skill-review.mjs</code
|
Votes call a separate service — see <code>vote-service/</code> — one per visitor, tracked by network
|
||||||
>. Votes call a separate service — see <code>vote-service/</code> — one per visitor, tracked by
|
source.
|
||||||
network source.
|
|
||||||
</footer>
|
</footer>
|
||||||
</main>
|
</main>
|
||||||
<script is:inline define:vars={{ serializedCatalog }}>
|
<script is:inline define:vars={{ serializedCatalog }}>
|
||||||
|
|||||||
Reference in New Issue
Block a user