rename

.github/instructions/pytesting.instructions.md

@@ -1,16 +1,18 @@
 ---
 name: Pytest Scaffolding Guidance
-description: Route tests edits to the Personal MCP pytest-scaffolding resource.
+description: Route tests edits to the Personal MCP pytesting resource.
 applyTo: 'tests/**'
 ---
 
-When editing files under `tests/`, use `resource://skills/pytest-scaffolding/document` as the primary guidance source for test scaffolding and pytest authoring decisions.
+When editing files under `tests/`, use `resource://skills/pytesting/document` as the primary guidance source for test scaffolding and pytest authoring decisions.
 
 Execution pattern:
 
-1. Load `resource://skills/pytest-scaffolding/document` first.
+1. Load `resource://skills/pytesting/document` first.
 2. Apply only the portions relevant to the file being edited.
 3. Keep tests focused, deterministic, and aligned with repository conventions.
 4. Include source-document links for any feature-level recommendation.
 
 If task intent is ambiguous, ask one clarifying question before editing.
+
+Be sure to also refer to the [testing page](../../docs/testing.md) page for design detail

.github/instructions/zensical-docs.instructions.md

@@ -7,3 +7,7 @@ applyTo: '**/*.md'
 When editing Markdown files in this repository, use the Zensical docs resource `resource://skills/zensical-docs/document` for relevant documentation authoring guidance.
 
 Prefer Zensical-native documentation conventions when they cover the need cleanly, while preserving expected MkDocs compatibility unless the Zensical guidance intentionally diverges.
+
+Always check to make sure the entries in `/home/john/Documents/prompts/zensical.toml` are up to date with any changes.
+
+Also ensure that top-level pages specify icons in their front matter

.github/prompts/plan-step1.prompt.md

@@ -61,7 +61,7 @@ Example valid ids:
 
 - `fastapi-uv-docker`
 - `zensical-docs`
-- `pytest-scaffolding`
+- `pytesting`
 
 Example invalid ids: