website-audit skill: Step 11 assumes a non-existent `designsystem/` folder (make it conditional)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 74/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- documentation
Research direction
Start with agent-pmo-skill/templates/skills/website-audit/SKILL.md at Step 11 and compare its wording with the neighboring conditional business-plan step. Make the design-system guidance conditional, then verify rendered or consumed copies do not emit the dead optional business_plan link; done means repos without those resources receive no missing-folder or broken-link caveat.
Written by the indexing model from the issue text.
Description
Where
agent-pmo-skill/templates/skills/website-audit/SKILL.md (Step 11 — Audit Design Compliance), currently line ~131:
Read the design system docs and view the design screens in the designsystem folder.
Problem
This line is unconditional — it tells the agent to read a designsystem/ folder that most consuming repos do not have. When the skill runs in a repo without one (e.g. Basilisk), the agent wastes a step looking for a folder that isn't there and has to caveat the audit report ("the designsystem folder doesn't exist").
The neighbouring business-plan step already uses the correct conditional phrasing ("If the repo has a business plan doc, take it into account"). Step 11 should match.
Note: in at least one rendered/consumed copy, the business-plan step also showed up as a hard-coded broken markdown link — [text](../../../business_plan/business_plan.md) — pointing at a path that doesn't exist in the consuming repo. Worth confirming the renderer never emits dead relative links for optional resources.
Suggested fix
Make Step 11 conditional, e.g.:
If the repo has a design system (design tokens, component docs, or design screens), review it and check the site for compliance. Otherwise, audit the live site's visual consistency directly (spacing, type scale, color usage, component reuse).
Impact
Low severity, but it makes every website-audit run in a design-system-less repo emit a spurious "missing folder" caveat. Filed from the Basilisk repo where the rendered skill carried both the dead business_plan link and the unconditional designsystem reference.
- Dominant language
- Nunjucks
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Nimblesite/AgentPMOWorkflow
-
Standard should mandate typeDiagram for model/type generation (remove Dart codegen assumptions) Openbug enhancement
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 50/100
-
Update release standards for build-time stamping and Microsoft platform-specific VSIX packaging Open
Difficulty 4/5 3-5 days Newbie friendliness 64/100
-
Difficulty 5/5 Over a week Newbie friendliness 32/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Nimblesite/AgentPMOWorkflow#1 · 1 comment ·
All issues in Nimblesite/AgentPMOWorkflow
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100