From f14dcf27237265d4e1b3bb3a5d69854872c0fcbb Mon Sep 17 00:00:00 2001 From: Prad Nukala Date: Mon, 5 Oct 2026 13:51:38 -0400 Subject: [PATCH] docs(skills): update paths to docs directory in problem-approach skill --- .claude/skills/problem-approach/SKILL.md | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/.claude/skills/problem-approach/SKILL.md b/.claude/skills/problem-approach/SKILL.md index 14175b9..1623eae 100644 --- a/.claude/skills/problem-approach/SKILL.md +++ b/.claude/skills/problem-approach/SKILL.md @@ -1,11 +1,11 @@ --- name: problem-approach -description: Write the `## Approach` section — a Mermaid flowchart that traces the submitted solution — for every docs solution page under apps/docs/content/ that lacks one, using the repo's exact placement and node conventions. Use when asked to add/implement/fill in missing approaches, draw the approach diagram for a problem page, or when `/problem-approach` is run. +description: Write the `## Approach` section — a Mermaid flowchart that traces the submitted solution — for every docs solution page under docs/ that lacks one, using the repo's exact placement and node conventions. Use when asked to add/implement/fill in missing approaches, draw the approach diagram for a problem page, or when `/problem-approach` is run. --- # Problem approach diagrams -Every solution page (`apps/docs/content/()//(problems)/_.mdx`) has a +Every solution page (`docs/()//(problems)/_.mdx`) has a hand-owned section before the script-owned one: ``` @@ -23,7 +23,7 @@ next `work/` push. 1. **Find the pages** (numbered pages with no `## Approach` heading): ```sh - grep -L '^## Approach' apps/docs/content/*/*.mdx + grep -rL '^## Approach' docs --include='[0-9]*_*.mdx' ``` 2. **For each page**, read `## Solution` and write the diagram from *that code* — the @@ -47,11 +47,13 @@ next `work/` push. ```` 4. **Check** each diagram by hand against the syntax rules below (the docs build does - not parse Mermaid — a broken diagram fails only in the browser), then run the - docs build once at the end and review the pages in `bun run dev`: + not parse Mermaid — a broken diagram fails only in the browser). The site is built + from prdlk/cs, which reads `docs/` over HTTP, so preview unpushed pages there + against this checkout (its `README` names the local-content switch), then build + once at the end: ```sh - cd apps/docs && bunx blume build --isolated && rm -rf .blume-verify + cd ../cs && bunx blume build --isolated && rm -rf .blume-verify ``` Pages with two languages (``) get **one** diagram, traced from the @@ -59,7 +61,7 @@ Python version. Pages with only JavaScript trace the JavaScript. ## Diagram conventions -Reference page: `apps/docs/content/(array)/15-3sum.mdx`. Every existing diagram +Reference page: `docs/(01-linear-structures)/two-pointers/(problems)/15_3sum.mdx`. Every existing diagram follows this shape: ```mermaid