nicegui component

.github/copilot-instructions.md

@@ -0,0 +1,49 @@
+# personal-mcp MCP Usage
+
+This repository is resource-first.
+
+- Canonical skill guidance lives in `docs/skills/<skill-id>/SKILL.md`.
+- The machine-facing skill contract is FastMCP's native `skill://` resource family.
+
+When a task appears to match a documented implementation pattern in `personal-mcp`, use this sequence:
+
+1. Prefer an already attached native skill resource.
+2. Otherwise browse native MCP resources and compare `skill://<name>/SKILL.md` descriptions.
+3. Read the best matching main skill file, or at most 2 candidate main files.
+4. Read `skill://<name>/_manifest` only when supporting material may be useful.
+5. Fetch only the relevant supporting paths from that manifest.
+6. Reconcile skill guidance with the actual repository code before proposing or making changes.
+
+Preferred MCP resource order:
+
+1. `skill://<name>/SKILL.md`
+2. `skill://<name>/_manifest` when needed
+3. `skill://<name>/<supporting-path>` for selected supporting files
+
+Selection rules:
+
+- Prefer the closest `name` and `description` match.
+- Keep context bounded; do not load many skill documents speculatively.
+- If confidence is low after reading at most two main files, ask one clarifying question before loading more context.
+
+Repository-specific guidance:
+
+- For tasks about adding or modifying a skill, use `skill://copilot-customization/SKILL.md` when relevant.
+- Keep skills provider-native; do not add custom skill catalogs, per-skill resource modules, or skill-specific discovery tools.
+
+
+## Python Checks
+
+After changes run these commands to confirm functionality. Resolve any errors
+
+```python
+uv run ruff check
+```
+
+```python
+uv run ty check
+```
+
+```python
+uv run pytest
+```

.github/instructions/fastmcp.instructions.md

@@ -10,6 +10,6 @@ For FastMCP implementation or protocol questions, load `skill://mcp-details/SKIL
 
 Inspect `skill://mcp-details/_manifest` only when a source reference is needed, then read the relevant supporting path. For FastMCP Python APIs, prefer the supporting reference that covers SDKs and FastMCP.
 
-This repository is resource-first and exposes resources as tools only as a fallback. In tool-only clients, use `list_resources` and `read_resource` with the same `skill://` URIs.
+This repository exposes skills through native MCP resources and prompts through native MCP prompt operations.
 
 Reconcile the skill guidance with the installed FastMCP version and the repository's existing implementation before editing.

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

@@ -1,46 +0,0 @@
-## Plan: Docs-First FastMCP End State
-
-Create a docs-first FastMCP architecture where all Markdown remains in docs/ as the only source of truth, each skill is Anthropic-compatible in its own directory, skill metadata lives in SKILL.md frontmatter, and packaged docs are served through importlib.resources so stdio deployments work from installed wheels.
-
-**Steps**
-1. Phase 1: Define the end-state content contract. Confirm canonical structure as docs/skills/<skill-id>/SKILL.md plus docs/skills/<skill-id>/references/..., with strict per-skill ownership and no metadata.yaml sidecar. Also define stable skill-id rules (kebab-case, immutable after release). Deliverable: update the current docs/ directory with the finalized end-state content contract from this step.
-2. Phase 1: Define SKILL.md frontmatter schema with Pydantic-compatible fields: id, version, name, description, tags, capabilities, depends_on, and references manifest entries. The references manifest must map logical reference ids to relative paths so each skill can reorganize references internally without changing global server code. Depends on step 1. Deliverable: update the current docs/ directory with the finalized SKILL.md frontmatter schema from this step.
-3. Phase 1: Define URI contract with explicit break-and-replace policy. Recommend resource://catalog/skills_index, resource://catalog/skills/{skill_id}, resource://skills/{skill_id}/document, resource://skills/{skill_id}/references/{ref_id}, and resource://docs/{path*}. Evolving URIs and reference ids requires direct replacement, with no aliases or compatibility shims. Depends on steps 1-2. Deliverable: update the current docs/ directory with the finalized URI contract and break-and-replace policy from this step.
-4. Phase 2: Build a docs registry loader that reads packaged docs via importlib.resources.files(...) Traversable APIs, parses SKILL.md frontmatter, validates schema, and creates an in-memory registry keyed by skill_id. Fail fast for duplicate ids, missing files, broken reference mappings, or invalid depends_on. Depends on steps 2-3.
-5. Phase 2: Register FastMCP resources from the registry using RFC6570 templates (including wildcard paths where appropriate), read-only/idempotent annotations, explicit mime types, and on_duplicate_resources="error" for startup safety. Depends on step 4.
-6. Phase 2: Add discovery surfaces as resources first, then tool fallback. Keep catalog discovery in resources, then add ResourcesAsTools for tool-only clients. Add thin discovery tools only for parity and optional BM25/regex tool search when catalog/tool volume grows enough to affect token efficiency. Define canonical fallback tool names (`list_resources`, `read_resource`, `search_patterns`, `get_pattern_by_id`, `get_skill_document_by_id`), research host-specific naming behavior for GitHub Copilot, Cursor, Claude Desktop, and generic MCP clients, and require client-side name mapping or intentionally documented aliases when providers expose namespaced wrappers. Depends on step 5.
-7. Phase 3: Implement packaging so docs/ is copied into package resource space at build time (wheel + sdist) while docs/ remains canonical in source control. Use importlib.resources at runtime only; avoid direct filesystem assumptions. Depends on steps 4-6.
-8. Phase 3: Remove materialization coupling between skill source modules and docs. The website build reads docs/ directly, while MCP reads packaged docs resources from the installed package. This preserves one authored source with two distribution surfaces. Depends on step 7.
-9. Phase 4: Add validation and CI gates: frontmatter schema checks, URI uniqueness checks, reference integrity checks, docs build check, package content check, and stdio smoke checks that read representative skill/document resources from an installed wheel. Depends on steps 5-8.
-10. Phase 4: Add long-term maintainability guardrails: architecture decision record for URI and schema contracts, skill authoring checklist, and release checklist for evolving references safely within one skill. Parallel with step 9 after core architecture is stable.
-
-
-
-**Relevant files**
-- /home/john/Documents/prompts/docs/index.md — Keep top-level docs entry and explain docs-first architecture contract.
-- /home/john/Documents/prompts/docs/skills — Canonical location for all skill content, including SKILL.md and references.
-- /home/john/Documents/prompts/pyproject.toml — Build inclusion rules for packaged markdown resources in wheel/sdist.
-- /home/john/Documents/prompts/src/personal_mcp/main.py — App/server startup wiring for resource registry initialization.
-- /home/john/Documents/prompts/src/personal_mcp/mcp.py — FastMCP instance composition and transform registration.
-- /home/john/Documents/prompts/src/personal_mcp/catalog/server.py — Catalog resource and fallback discovery behavior.
-- /home/john/Documents/prompts/src/personal_mcp/skills/document_loader.py — Replace file-path assumptions with importlib.resources docs registry loading.
-- /home/john/Documents/prompts/src/personal_mcp/web/materialize_skill_docs.py — De-scope or retire materialization once docs-first runtime is authoritative.
-
-**Verification**
-1. Run uv run zensical build to verify docs/ remains valid and site output is stable.
-2. Run uv run pytest -q with tests that validate frontmatter parsing, URI generation, reference mapping, and catalog responses.
-3. Run a packaging integrity check using importlib.resources.files(...) to confirm packaged docs resources exist and are readable from an installed wheel.
-4. Run a stdio MCP smoke test that lists resources and reads at least one skill document and one reference document.
-5. Run fallback-client smoke tests verifying list_resources/read_resource tools work and return expected metadata for both static and templated resources, and that GitHub Copilot, Cursor, Claude Desktop, and protocol-level SDK tests use canonical tool names or documented mapped aliases.
-
-**Decisions**
-- Anthropic compatibility: strict skill directory pattern with SKILL.md and references subtree.
-- Metadata strategy: YAML frontmatter in SKILL.md (no separate metadata file).
-- Discovery strategy: resource-first catalog with tool fallback for tool-only MCP clients.
-- Included scope: ideal end-state architecture, contracts, validation, and packaging for stdio operation.
-- Excluded scope: migration mechanics from current implementation, backward-compat shim details, and docs visual redesign.
-
-**Further Considerations**
-1. Prefer recursive references support under each skill plus frontmatter manifest ids, so skill teams can reorganize internal reference folders without URI churn.
-2. Define a hard rule that skill_id and directory name must match exactly to eliminate namespace/slug drift classes of bugs.
-3. Do not provide URI aliases; client updates must track canonical URI contract changes directly.

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

@@ -1,169 +0,0 @@
-**Phase 3 Results: Packaging Contract and Surface Decoupling (Wheel/sdist Resources + Docs-Only Authoring)**
-
-This section finalizes Phase 3 by defining how authored docs are packaged as runtime resources, how runtime loading avoids filesystem assumptions, and how website and MCP distribution surfaces are decoupled while sharing one authored source.
-
-### Greenfield Framing (Normative)
-
-This Phase 3 design assumes a full refactor with intentional break-and-replace behavior:
-
-1. No compatibility shims, aliases, adapter layers, or dual-read runtime paths.
-2. No runtime dependency on repository checkout layout.
-3. Runtime docs access is package-resource-only.
-4. Canonical authoring remains in `docs/` in source control.
-
-### Research Baseline (Packaging + Runtime)
-
-Authoritative references used for this phase:
-
-1. Python `importlib.resources` docs (`files`, `Traversable`, and zip-safe behavior)
-2. Python packaging guidance for wheel/sdist data inclusion
-3. Hatchling build target configuration guidance for including non-code files
-4. Existing repository constraints from Steps 4-5 (registry-first, deterministic startup, resource-first discovery)
-
-Best-practice conclusions applied to this design:
-
-1. Package docs as build artifacts so runtime reads work from installed wheels.
-2. Keep docs source-of-truth in one place (`docs/`) and project into package resource space at build time.
-3. Avoid `Path(__file__)`/repo-root probing in runtime paths.
-4. Enforce parity across wheel and sdist so local/dev/prod behavior does not drift.
-
-### Phase 3 Responsibilities (Normative)
-
-Phase 3 MUST:
-
-1. Ensure authored markdown under `docs/` is included in wheel and sdist artifacts.
-2. Ensure runtime docs registry/document reads use `importlib.resources` only.
-3. Ensure MCP runtime behavior is independent of current working directory or checkout structure.
-4. Ensure website docs build continues to consume source `docs/` directly.
-5. Remove materialization/path-probing coupling from runtime loader code.
-6. Preserve deterministic packaged docs layout for registry/resource URI generation.
-
-### Packaging Contract (Wheel + sdist)
-
-Canonical packaging behavior:
-
-1. Source-authored docs remain at repository root: `docs/`.
-2. Build projects docs into package resource space under `personal_mcp/docs/` inside artifacts.
-3. Runtime anchor for docs loading is `importlib.resources.files("personal_mcp").joinpath("docs")`.
-4. Build artifacts MUST include:
-   - top-level docs pages used by discovery/overview
-   - `docs/skills/<skill-id>/SKILL.md`
-   - `docs/skills/<skill-id>/references/**`
-
-Parity requirements:
-
-1. Wheel and sdist contain equivalent docs content for runtime use.
-2. Missing docs resources in either artifact is a hard validation failure.
-
-### Build-System Plan (pyproject + build)
-
-Primary target file:
-
-1. `pyproject.toml`
-
-Configuration goals:
-
-1. Add explicit build inclusion rules so docs resources are shipped in wheel artifacts.
-2. Add explicit sdist inclusion rules so docs are present for source builds.
-3. Keep inclusion deterministic and auditable (no implicit glob side effects beyond intended docs content).
-4. Ensure packaged destination path matches runtime anchor (`personal_mcp/docs`).
-
-Implementation note:
-
-1. Use Hatchling-native inclusion mapping (for example force-include or equivalent target-level include mapping) to project `docs/` into package resource space.
-2. Prefer one clear packaging path over multiple fallback packaging mechanisms.
-
-### Runtime Loader Contract (No Filesystem Assumptions)
-
-Primary target file:
-
-1. `src/personal_mcp/skills/document_loader.py`
-
-Required runtime behavior:
-
-1. Remove repository-root discovery helpers and path-probing candidates.
-2. Remove metadata-based document path overrides that bypass canonical skill layout.
-3. Resolve SKILL and reference documents via package-resource-relative paths only.
-4. Keep reads UTF-8 and deterministic.
-5. Raise explicit errors for missing packaged resources; no fallback probing.
-
-Prohibited runtime behavior:
-
-1. No `Path(__file__).resolve().parents[...]` lookup for docs.
-2. No implicit fallback to source-tree `docs/` during runtime reads.
-3. No slug-guessing or namespace substitution for path recovery.
-
-### Surface Decoupling Contract (Website vs MCP)
-
-Website surface:
-
-1. Website build pipeline consumes source `docs/` directly (`uv run zensical build`).
-2. Static output (`site/`) remains a build artifact served by web mounting logic.
-
-MCP surface:
-
-1. MCP runtime serves docs from packaged resources loaded by registry/resource handlers.
-2. MCP does not read `site/` and does not depend on website build artifacts.
-
-Decoupling guarantees:
-
-1. One authored source (`docs/`), two distribution surfaces (website + MCP runtime).
-2. Changes to website serving do not alter MCP resource loading semantics.
-3. Changes to MCP runtime loader do not require website materialization logic.
-
-### Integration Plan for Existing Modules
-
-Primary integration targets:
-
-1. `pyproject.toml`: add wheel/sdist docs inclusion mapping.
-2. `src/personal_mcp/skills/document_loader.py`: replace filesystem probing with package-resource loading.
-3. `src/personal_mcp/main.py`: keep startup composition deterministic once registry/resource registration is in place.
-4. `src/personal_mcp/mcp.py`: maintain registry-driven resource composition as canonical runtime surface.
-5. `src/personal_mcp/web/docs_mount.py`: continue static-site mount behavior without coupling to MCP runtime docs loading.
-
-Cleanup targets:
-
-1. Remove obsolete references to materialization-only modules if no longer present/used.
-2. Remove dead code paths that attempt source-tree fallback loading.
-
-### Validation and Test Plan (Phase 3 Scope)
-
-Build/package validation:
-
-1. Build wheel and sdist in CI/local.
-2. Inspect artifacts to confirm `personal_mcp/docs/**` exists and includes representative skill/reference files.
-3. Install built wheel in isolated environment and verify resource reads via `importlib.resources.files(...)`.
-
-Runtime validation:
-
-1. Run MCP in an environment where repo-root docs paths are unavailable and confirm reads still succeed.
-2. Verify representative URIs resolve (skill document and reference document).
-3. Confirm startup fails clearly if required packaged docs resources are missing.
-
-Decoupling validation:
-
-1. Run `uv run zensical build` to verify website pipeline still consumes source `docs/`.
-2. Confirm MCP runtime does not require `site/` presence.
-3. Confirm web static serving behavior is unchanged when docs are built.
-
-Expected command path in this repo:
-
-1. `uv run pytest -q`
-2. `uv run zensical build`
-
-### Acceptance Criteria for Phase 3 Completion
-
-Phase 3 is complete when all are true:
-
-1. Wheel and sdist include docs resources in deterministic package paths.
-2. Runtime docs loading works from installed artifacts using `importlib.resources` only.
-3. Runtime docs loading has no checkout-path dependency and no fallback probing.
-4. Website docs build remains source-docs-driven and independent of MCP runtime loading.
-5. No compatibility shims, aliases, or dual runtime loader paths exist.
-
-### Non-goals for Phase 3
-
-1. No Step 6 discovery-tool fallback implementation details.
-2. No URI aliasing or backward-compat transition mechanics.
-3. No redesign of skill frontmatter/schema contracts already finalized in earlier steps.
-4. No web UI visual redesign or docs IA overhaul.

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

@@ -1,84 +0,0 @@
-**Step 1 Results: End-State Content Contract**
-
-This section finalizes Step 1 by defining the canonical authored content model.
-
-### Step Deliverable
-
-- Update the current `docs/` directory with the finalized Step 1 content contract from this document.
-
-### Canonical source of truth
-
-- All authored Markdown lives under `docs/`.
-- MCP resources and static docs are two distribution surfaces of the same authored files.
-- No parallel authored markdown is allowed in `src/` or other package-only paths.
-
-### Canonical skill shape (Anthropic-compatible)
-
-Each skill is one directory under `docs/skills/`:
-
-```text
-docs/
-	skills/
-		<skill-id>/
-			SKILL.md
-			references/
-				... (one or more markdown files, optional nested folders)
-```
-
-Rules:
-
-- `SKILL.md` is required for every skill.
-- `references/` is the only place for skill-specific supporting docs.
-- Nested folders inside `references/` are allowed so a skill can reorganize internals without changing global architecture.
-- Skill directories are independent ownership boundaries; no cross-skill file writes.
-
-### File placement and ownership boundaries
-
-- Top-level project docs stay in `docs/*.md`.
-- Skill docs stay in `docs/skills/<skill-id>/...`.
-- A skill may link to other skills, but must not store content inside another skill's directory.
-- Server/runtime code may index and serve docs, but must not be the source of authored markdown.
-
-### Metadata location constraint
-
-- Skill metadata is embedded in YAML frontmatter in `SKILL.md`.
-- No `metadata.yaml` sidecar in the end state.
-- Reference lookup metadata (ids to relative paths) is declared from `SKILL.md` frontmatter, not inferred as a hidden global convention.
-
-### Skill-id contract (change-friendly)
-
-`skill-id` is the public identifier and SHOULD satisfy all rules below:
-
-- Format: lowercase kebab-case only.
-- Character set: `a-z`, `0-9`, and `-`.
-- Must start with a letter.
-- No underscores, spaces, dots, or uppercase characters.
-- Directory name should equal `skill-id` in each committed revision.
-- Frontmatter `id` should equal directory name in each committed revision.
-- Treat `skill-id` as immutable after release; any rename is a breaking replacement and clients must move to the new id.
-
-Example valid ids:
-
-- `fastapi-uv-docker`
-- `zensical-docs`
-- `pytesting`
-
-Example invalid ids:
-
-- `fastapi_uv_docker` (underscore)
-- `Zensical-Docs` (uppercase)
-- `docs.zensical` (dot)
-
-### Invariants this contract guarantees
-
-- One authored source tree (`docs/`) for both website and MCP.
-- One skill directory maps to one skill identity per revision.
-- Namespace/slug drift is minimized by keeping directory and frontmatter ids aligned per revision.
-- Per-skill reference structure can evolve without changing cross-skill architecture.
-- Packaging for stdio is deterministic because authored content is path-stable.
-
-### Non-goals for Step 1
-
-- No URI versioning policy details yet (handled in Step 3).
-- No full frontmatter schema details yet (handled in Step 2).
-- No migration instructions from current architecture (out of scope for this plan).

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

@@ -1,298 +0,0 @@
-**Step 2 Results: SKILL.md Frontmatter and FastMCP Metadata Contract**
-
-This section finalizes Step 2 by defining the canonical SKILL.md frontmatter schema, separating Anthropic-supported fields from repository extension fields, and mapping frontmatter to FastMCP-native metadata surfaces for resources and tools.
-
-### Step Deliverable
-
-- Update the current `docs/` directory with the finalized Step 2 frontmatter and metadata contract content from this document.
-
-### Anthropic Frontmatter Support (Research Baseline)
-
-Across Anthropic API and Agent Skills specification surfaces:
-
-- Required for custom skill bundles: `name`, `description`.
-- `name` constraints (Agent Skills API docs): 1-64 chars, lowercase letters/numbers/hyphens, no XML tags, and must not use reserved words `anthropic` or `claude`.
-- `description` constraints (Agent Skills API docs): 1-1024 chars, non-empty, no XML tags.
-
-Portable optional fields from the Agent Skills specification:
-
-- `license`
-- `compatibility`
-- `metadata`
-- `allowed-tools` (experimental)
-
-Claude Code-specific optional fields (supported by Claude Code skills docs):
-
-- `when_to_use`, `argument-hint`, `arguments`
-- `disable-model-invocation`, `user-invocable`
-- `allowed-tools`, `disallowed-tools`
-- `model`, `effort`, `context`, `agent`, `hooks`, `paths`, `shell`
-
-Contract decision for this repository:
-
-- Treat `name` and `description` as required in all SKILL.md files, even where a client could infer defaults.
-- Keep Anthropic-facing semantics in standard fields and keep MCP indexing metadata in a namespaced extension block.
-- Preserve forward compatibility by allowing additive optional metadata fields over time.
-
-### Canonical Frontmatter Schema For This Repository
-
-Use this exact two-layer pattern:
-
-1. Anthropic layer (portable): top-level fields intended for Anthropic/Agent Skills behavior.
-2. Repository layer (runtime indexing): one namespaced block, `x-personal-mcp`, for MCP catalog and routing metadata.
-
-Canonical shape:
-
-```yaml
----
-name: <skill-id>
-description: <what this skill does and when to use it>
-
-# Optional Anthropic/Agent Skills fields (use only when needed)
-when_to_use: <extra trigger guidance>
-allowed-tools: <space-separated string or YAML list>
-disable-model-invocation: false
-user-invocable: true
-license: <optional>
-compatibility: <optional>
-
-# Repository-specific metadata (authoritative for MCP indexing)
-x-personal-mcp:
-  id: <skill-id>
-  version: <semver>
-  tags:
-    - <tag>
-  capabilities:
-    - resource://skills/<skill-id>/document
-  depends_on: []
-  references:
-    <ref-id>:
-      path: references/<file>.md
-      mime_type: text/markdown
-      title: <short title>
----
-```
-
-### Repository Metadata Field Rules (`x-personal-mcp`)
-
-- `id` required: must follow Step 1 skill-id rules and equal directory name.
-- `version` required: semantic version string.
-- `tags` optional: list of kebab-case discovery labels.
-- `capabilities` required: list of MCP URIs this skill publishes.
-- `depends_on` optional: list of other skill ids.
-- `references` optional map:
-    - key is `ref-id` (kebab-case).
-    - `path` is a skill-relative markdown path and must stay inside the same skill directory.
-    - nested folders under `references/` are allowed.
-    - `mime_type` defaults to `text/markdown` if omitted.
-    - `title` is an optional display label.
-    - renaming `ref-id` values is allowed when needed; optional aliases may be used during transitions.
-
-### Pydantic Models For Frontmatter Validation
-
-Define the Step 2 contract with Pydantic v2 models and change-friendly validation.
-
-Normative model sketch:
-
-```python
-from __future__ import annotations
-
-import re
-from pathlib import PurePosixPath
-from typing import Any
-
-from pydantic import BaseModel, ConfigDict, Field, field_validator, model_validator
-
-SKILL_ID_RE = re.compile(r"^[a-z][a-z0-9-]*$")
-SEMVER_RE = re.compile(r"^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:[-+][0-9A-Za-z.-]+)?$")
-
-
-class ReferenceEntry(BaseModel):
-    model_config = ConfigDict(extra="ignore", str_strip_whitespace=True)
-
-    path: str
-    mime_type: str = "text/markdown"
-    title: str | None = None
-
-    @field_validator("path")
-    @classmethod
-    def validate_reference_path(cls, value: str) -> str:
-        p = PurePosixPath(value)
-        if p.is_absolute() or ".." in p.parts:
-            raise ValueError("reference path must be a relative in-skill path")
-        if not str(p).startswith("references/"):
-            raise ValueError("reference path must stay under references/")
-        if p.suffix.lower() != ".md":
-            raise ValueError("reference path must target a markdown file")
-        return str(p)
-
-
-class PersonalMcpMetadata(BaseModel):
-    model_config = ConfigDict(extra="ignore", str_strip_whitespace=True)
-
-    id: str
-    version: str
-    tags: list[str] = Field(default_factory=list)
-    capabilities: list[str] = Field(min_length=1)
-    depends_on: list[str] = Field(default_factory=list)
-    references: dict[str, ReferenceEntry] = Field(default_factory=dict)
-
-    @field_validator("id")
-    @classmethod
-    def validate_id(cls, value: str) -> str:
-        if not SKILL_ID_RE.fullmatch(value):
-            raise ValueError("id must be lowercase kebab-case and start with a letter")
-        return value
-
-    @field_validator("version")
-    @classmethod
-    def validate_version(cls, value: str) -> str:
-        if not SEMVER_RE.fullmatch(value):
-            raise ValueError("version must be semver")
-        return value
-
-    @field_validator("depends_on")
-    @classmethod
-    def validate_depends_on(cls, value: list[str]) -> list[str]:
-        for dep in value:
-            if not SKILL_ID_RE.fullmatch(dep):
-                raise ValueError(f"invalid depends_on skill id: {dep}")
-        return value
-
-    @field_validator("references")
-    @classmethod
-    def validate_reference_ids(cls, value: dict[str, ReferenceEntry]) -> dict[str, ReferenceEntry]:
-        for ref_id in value:
-            if not SKILL_ID_RE.fullmatch(ref_id):
-                raise ValueError(f"invalid reference id: {ref_id}")
-        return value
-
-    @model_validator(mode="after")
-    def ensure_primary_capability(self) -> "PersonalMcpMetadata":
-        expected = f"resource://skills/{self.id}/document"
-        if expected not in self.capabilities:
-            raise ValueError(f"capabilities must include {expected}")
-        return self
-
-
-class SkillFrontmatter(BaseModel):
-    model_config = ConfigDict(extra="ignore", str_strip_whitespace=True)
-
-    # Anthropic/Agent Skills fields
-    name: str = Field(min_length=1, max_length=64)
-    description: str = Field(min_length=1, max_length=1024)
-    when_to_use: str | None = None
-    allowed_tools: str | list[str] | None = Field(default=None, alias="allowed-tools")
-    disallowed_tools: str | list[str] | None = Field(default=None, alias="disallowed-tools")
-    disable_model_invocation: bool | None = Field(default=None, alias="disable-model-invocation")
-    user_invocable: bool | None = Field(default=None, alias="user-invocable")
-    argument_hint: str | None = Field(default=None, alias="argument-hint")
-    arguments: str | list[str] | None = None
-    license: str | None = None
-    compatibility: str | None = None
-    metadata: dict[str, str] | None = None
-
-    # Repository extension block
-    x_personal_mcp: PersonalMcpMetadata = Field(alias="x-personal-mcp")
-
-    @field_validator("name")
-    @classmethod
-    def validate_name(cls, value: str) -> str:
-        if not SKILL_ID_RE.fullmatch(value):
-            raise ValueError("name must be lowercase kebab-case and start with a letter")
-        if "anthropic" in value or "claude" in value:
-            raise ValueError("name must not contain reserved words anthropic or claude")
-        return value
-
-    @model_validator(mode="after")
-    def cross_validate(self) -> "SkillFrontmatter":
-        if self.x_personal_mcp.id != self.name:
-            raise ValueError("x-personal-mcp.id must exactly match name")
-        return self
-
-
-def validate_skill_frontmatter(raw: dict[str, Any], skill_dir_name: str) -> SkillFrontmatter:
-    model = SkillFrontmatter.model_validate(raw)
-    if model.name != skill_dir_name:
-        raise ValueError("frontmatter name must exactly match skill directory name")
-    return model
-```
-
-Validation behavior contract:
-
-- Validate required core fields and relationships during registry load before FastMCP resource/tool registration.
-- Allow unknown additive fields so frontmatter can evolve without blocking startup.
-- Treat hard contract violations (missing required fields, invalid ids, broken required mappings) as startup errors.
-- Treat non-critical compatibility issues as warnings when possible.
-- Error messages should include skill path and failing field for CI readability.
-
-Projection mode contract (for Anthropic API upload pipelines):
-
-- Parse with `SkillFrontmatter` first.
-- Emit Anthropic-safe frontmatter with standard fields only.
-- Serialize repository metadata into standard `metadata` as namespaced keys.
-- Preserve the canonical authored source in `x-personal-mcp`; projection output is a build artifact.
-
-### Anthropic Upload Compatibility Rule
-
-- Anthropic documentation guarantees behavior for standard frontmatter fields but does not explicitly guarantee handling of arbitrary unknown top-level keys.
-- Therefore, publishing pipelines that target strict API compatibility should support a projection mode that emits only standard frontmatter fields for upload.
-- In projection mode, repository extension metadata is serialized into the standard `metadata` field (for example as namespaced keys or JSON-encoded values), while source-of-truth authoring remains in `x-personal-mcp`.
-
-### FastMCP Native Metadata Surfaces (Research Baseline)
-
-Resources (`@mcp.resource` and templates) support native definition metadata:
-
-- `name`, `description`, `mime_type`, `tags`
-- `annotations` (`readOnlyHint`, `idempotentHint`)
-- `icons`
-- `meta` (custom metadata passed through to the MCP client resource object)
-- `version`
-- `enabled` (deprecated in v3; prefer server-level `mcp.enable()` / `mcp.disable()`)
-
-Resources support runtime metadata:
-
-- `ResourceContent.meta` (item-level)
-- `ResourceResult.meta` (result-level `_meta`)
-
-Tools (`@mcp.tool`) support native definition metadata:
-
-- `name`, `description`, `tags`
-- `annotations` (`title`, `readOnlyHint`, `destructiveHint`, `idempotentHint`, `openWorldHint`)
-- `icons`
-- `meta` (custom metadata passed through to the MCP client tool object)
-- `version`
-- `timeout`, `output_schema`, `run_in_thread`
-- `enabled` (deprecated in v3; prefer server-level `mcp.enable()` / `mcp.disable()`)
-
-Tools support runtime metadata:
-
-- `ToolResult.meta` (execution-level metadata for each call)
-
-### Frontmatter To FastMCP Mapping Contract
-
-At server startup, map `x-personal-mcp` fields into FastMCP registration as follows:
-
-- `x-personal-mcp.id` -> canonical URI namespace and identity checks.
-- `description` -> default `description` for the primary skill document resource.
-- `x-personal-mcp.tags` -> `tags` on resources/tools.
-- `x-personal-mcp.version` -> `version` on resources/tools.
-- `x-personal-mcp.capabilities` -> registered URI list plus catalog exposure.
-- `x-personal-mcp.references[*]` -> resource templates or concrete resources with:
-  - `mime_type` from reference entry (or default)
-  - `meta` including `skill_id`, `ref_id`, and source `path`
-  - read-only annotations for documentation resources
-- `x-personal-mcp.depends_on` -> catalog dependency graph metadata and validation checks.
-
-### Invariants This Contract Guarantees
-
-- Anthropic-required frontmatter stays valid for custom skill upload and Claude Code loading.
-- MCP-specific metadata remains embedded in SKILL.md frontmatter, with no `metadata.yaml` sidecar.
-- FastMCP registration uses only native metadata fields for resources/tools.
-- Reference ids and metadata can evolve with low-friction updates while internal file layout under `references/` stays refactor-friendly.
-
-### Non-goals For Step 2
-
-- No URI versioning/deprecation rollout policy details (handled in Step 3).
-- No migration script design from existing `metadata.yaml` files.
-- No runtime caching/indexing performance tuning details.

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

@@ -1,114 +0,0 @@
-**Step 3 Results: URI Contract and Compatibility Policy**
-
-This section finalizes Step 3 by defining the canonical resource URI contract, template parameter rules, and explicit compatibility/versioning policy for URIs and reference ids.
-
-### Step Deliverable
-
-- Update the current `docs/` directory with the finalized Step 3 URI contract and compatibility policy content from this document.
-
-### Canonical URI Surface (Normative)
-
-The public, preferred URIs are:
-
-1. `resource://catalog/skills_index`
-2. `resource://catalog/skills/{skill_id}`
-3. `resource://skills/{skill_id}/document`
-4. `resource://skills/{skill_id}/references/{ref_id}`
-5. `resource://docs/{path*}`
-
-Contract intent:
-
-- Catalog URIs are discovery surfaces.
-- Skill URIs are primary per-skill guidance surfaces.
-- Docs wildcard URI is a direct authored-markdown access surface under `docs/`.
-
-### URI Semantics
-
-`resource://catalog/skills_index`
-
-- Returns a compact list of skill records for discovery.
-- One entry per `skill_id`.
-- Must include enough metadata for client-side selection (at minimum id, name, description, tags, capabilities).
-
-`resource://catalog/skills/{skill_id}`
-
-- Returns one normalized record for `skill_id`.
-- Must include canonical document URI and declared reference ids.
-- Returns not-found when `skill_id` does not exist.
-
-`resource://skills/{skill_id}/document`
-
-- Returns the canonical `SKILL.md` authored content for that skill.
-- `skill_id` must match Step 1 stable id rules.
-
-`resource://skills/{skill_id}/references/{ref_id}`
-
-- Returns one reference document declared in the skill frontmatter references manifest.
-- `ref_id` is the stable public handle for that reference document.
-
-`resource://docs/{path*}`
-
-- Returns authored markdown at a normalized relative path under `docs/`.
-- Supports nested paths via RFC6570 wildcard expansion.
-- Typical examples: `index.md`, `usage.md`, `skills/<skill-id>/SKILL.md`, `skills/<skill-id>/references/<file>.md`.
-
-### Template Parameter and Validation Rules
-
-`skill_id`
-
-- Lowercase kebab-case.
-- Must satisfy Step 1 stable id rules.
-
-`ref_id`
-
-- Lowercase kebab-case.
-- Must be declared in the skill’s references manifest.
-
-`path*`
-
-- Relative POSIX path only.
-- No leading slash.
-- No `..` traversal segments.
-- Resolves only inside `docs/`.
-- This surface is markdown-only in end state (`.md` files).
-
-### URI Versioning Policy
-
-Default rule:
-
-- Keep URIs unversioned by default.
-- Allow URI and payload updates when they improve clarity or implementation simplicity.
-
-Breaking-change rule:
-
-- Breaking changes use direct replacement of the canonical URI family.
-- No compatibility aliases or dual URI families are maintained in this greenfield phase.
-
-FastMCP version metadata usage:
-
-- Resource `version` metadata MAY be used for implementation/version discovery.
-- URI readability and maintainability remain the primary contract.
-
-### Reference ID Compatibility Policy
-
-`ref_id` is the public identifier for a reference document, separate from file path.
-
-Rules:
-
-- Prefer keeping `ref_id` stable when practical.
-- File paths may change without URI churn as long as the mapped `ref_id` resolves.
-- If a reference is renamed, introduce a new `ref_id` and treat the old one as retired.
-- Avoid reusing retired `ref_id` values for unrelated content.
-
-### Invariants This Contract Guarantees
-
-- One canonical URI pattern per core capability surface.
-- Fast, low-friction URI evolution through direct replacement of canonical URIs.
-- A single canonical catalog URI family with no alias maintenance overhead.
-- Reference mappings can evolve with minimal churn.
-
-### Non-goals For Step 3
-
-- No implementation-specific transform wiring details (`VersionFilter`, mounts, provider composition).
-- No migration script mechanics for auto-generating aliases.
-- No authorization policy design for URI-level access control.

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

@@ -1,248 +0,0 @@
-**Step 4 Results: Docs Registry Loader Design (importlib.resources + Fail-Fast Validation)**
-
-This section finalizes Step 4 by defining a production-ready docs registry loader that reads packaged docs through Python resource APIs, parses SKILL.md frontmatter, validates schema and cross-links, and builds an immutable in-memory registry keyed by skill_id.
-
-### Greenfield Framing (Normative)
-
-This Step 4 design is for the greenfield target state:
-
-1. No legacy metadata sidecars (`metadata.yaml`) are part of the runtime contract.
-2. No dual-loader compatibility path is required.
-3. Registry loading from packaged resources is the only runtime source of truth.
-4. Compatibility shims are prohibited.
-
-### Research Baseline (Python + Design Guidance)
-
-Authoritative references used for this step:
-
-1. Python `importlib.resources` docs (`files`, `as_file`, `Traversable` APIs)
-2. Python `importlib.resources.abc` docs (`Traversable`, path traversal semantics, joinpath compatibility notes)
-3. Pydantic v2 model/validation docs (`model_validate`, `ValidationError`, strictness and extra handling)
-4. Python packaging guidance for including package data in wheels/sdists
-
-Best-practice conclusions applied to this design:
-
-1. Prefer `importlib.resources.files(<package>).joinpath(...)` over filesystem assumptions so stdio deployments from installed wheels work.
-2. Treat resources as potentially non-filesystem artifacts (zip-import compatible); only use `as_file(...)` when an actual OS path is required.
-3. Validate metadata with explicit Pydantic models and fail startup on contract violations.
-4. Keep registry load deterministic (sorted traversal, stable error messages, no hidden fallback mutations).
-5. Resolve references via manifest ids declared in frontmatter, not by global file conventions.
-
-### Loader Responsibilities (Normative)
-
-The Step 4 loader MUST:
-
-1. Read canonical docs from package resources (not repo-root paths).
-2. Discover all skill directories under `docs/skills/` in packaged resources.
-3. For each skill, read and parse `SKILL.md` frontmatter.
-4. Validate frontmatter using the Step 2 schema contract.
-5. Validate directory/id invariants from Step 1 (directory name equals frontmatter id).
-6. Validate URI/reference semantics from Step 3 assumptions.
-7. Build a single in-memory registry keyed by `skill_id`.
-8. Fail fast on any integrity error before FastMCP resource registration.
-9. Precompute compact discovery projections so index resources can be served without reading full markdown bodies at request time.
-
-### Package Resource Contract
-
-Runtime anchor:
-
-1. The loader resolves content from an importable package anchor, for example `personal_mcp`.
-2. Docs root is located as `files(anchor).joinpath("docs")` when docs are packaged at package root, or an equivalent configured subpath.
-3. Skill root is `docs/skills`.
-
-Resource assumptions:
-
-1. `SKILL.md` is UTF-8 text.
-2. Reference files declared in frontmatter are UTF-8 markdown by default unless otherwise declared.
-3. Path resolution always remains inside the same skill directory.
-
-### Registry Data Model
-
-Build immutable runtime records with explicit structure:
-
-1. `SkillRecord`
-   - `skill_id`
-   - `name`
-   - `description`
-   - `version`
-   - `tags`
-   - `capabilities`
-   - `depends_on`
-   - `document_uri`
-   - `document_relpath` (canonical resource-relative path)
-   - `references` map keyed by `ref_id`
-2. `ReferenceRecord`
-   - `ref_id`
-   - `uri`
-   - `relpath`
-   - `mime_type`
-   - `title`
-3. `DocsRegistry`
-   - `skills_by_id: dict[str, SkillRecord]`
-   - `skills_in_load_order: list[str]` (deterministic ordering)
-   - helper indexes for catalog payload generation
-   - `skills_summary_in_load_order: list[SkillSummaryRecord]` for progressive discovery responses
-   - filter indexes (for example by tag/capability) derived once at startup
-
-4. `SkillSummaryRecord`
-   - `skill_id`
-   - `name`
-   - `description`
-   - `tags`
-   - `capabilities`
-   - `document_uri`
-   - optional `version`
-
-Immutability rule:
-
-1. Once built, registry records are treated as read-only for the process lifetime.
-2. No runtime mutation during requests; refresh only via process restart.
-
-### Frontmatter Parsing Contract
-
-`SKILL.md` parse steps:
-
-1. Read full markdown text from resource.
-2. Parse YAML frontmatter block at file start (between the first two `---` delimiters).
-3. Parse YAML with safe loader semantics.
-4. Validate parsed object with Step 2 Pydantic model(s).
-5. Preserve markdown body as document content payload.
-
-Parsing failure behavior:
-
-1. Missing frontmatter block: startup error.
-2. Invalid YAML: startup error with skill path and YAML parser detail.
-3. Missing required fields (`name`, `description`, `x-personal-mcp` contract fields): startup error.
-
-### Validation Pipeline (Fail-Fast)
-
-Validation happens in this order:
-
-1. Structural discovery validation
-   - skill directory exists under `docs/skills`
-   - required `SKILL.md` exists for each discovered skill
-2. Schema validation
-   - Pydantic frontmatter validation for all required and constrained fields
-3. Identity validation
-   - frontmatter `name` equals `x-personal-mcp.id`
-   - frontmatter id equals skill directory name
-4. Reference manifest validation
-   - unique `ref_id` keys per skill
-   - each manifest path is relative, in-skill, and under `references/`
-   - each manifest target exists and is a file
-5. Dependency graph validation
-   - every `depends_on` target exists in discovered skill set
-   - no self-dependency
-   - cycle detection enabled (hard error on cycle)
-6. Capability sanity checks
-   - required primary capability `resource://skills/{skill_id}/document` is present
-7. Global uniqueness checks
-   - no duplicate `skill_id`
-   - no duplicate canonical resource URIs generated from registry
-8. Discovery payload checks
-   - summary fields required by catalog index are present and non-empty
-   - summary generation does not require reading markdown body content during request handling
-
-### Error Model and Reporting
-
-Error handling contract:
-
-1. Collect errors per validation phase for clarity, then raise one startup exception containing all findings.
-2. Error messages must include:
-   - skill id (when known)
-   - packaged relative path
-   - violated rule
-   - actionable fix hint
-3. If any error exists, registry is not published and FastMCP resource registration does not proceed.
-
-Recommended exception shape:
-
-1. `DocsRegistryValidationError(errors: list[RegistryIssue])`
-2. `RegistryIssue` fields: `code`, `message`, `skill_id`, `path`, `hint`
-
-### Determinism and Runtime Safety
-
-Determinism rules:
-
-1. Traverse directories in sorted order.
-2. Normalize all stored relative paths to POSIX form.
-3. Normalize ids/tags exactly once at parse boundary.
-4. Produce stable catalog ordering to reduce client churn.
-5. Produce stable summary projections and filter indexes from the same normalized source records.
-
-Runtime safety rules:
-
-1. No dependence on `Path(__file__)` or repository root.
-2. No ad-hoc fallback probing across multiple locations.
-3. No lazy validation deferred until first request.
-
-### Integration Plan for Existing Modules
-
-Primary integration target:
-
-1. Implement the canonical package-resource-based registry loader in `src/personal_mcp/skills/document_loader.py` as the only supported runtime loader path.
-
-Catalog integration:
-
-1. Update `src/personal_mcp/catalog/server.py` to consume the shared in-memory registry as the only catalog data source.
-2. Keep catalog payload normalization deterministic and sourced from registry records only.
-
-Startup wiring:
-
-1. Initialize registry once during app/server startup in `src/personal_mcp/main.py` or equivalent composition point.
-2. Pass registry to resource registration step (Step 5).
-
-### Proposed Loader API Surface
-
-Use a small, testable API:
-
-1. `load_docs_registry(*, package_anchor: str, docs_root: str = "docs") -> DocsRegistry`
-2. `read_skill_document(registry: DocsRegistry, skill_id: str) -> DocumentPayload`
-3. `read_skill_reference(registry: DocsRegistry, skill_id: str, ref_id: str) -> DocumentPayload`
-
-Design constraints:
-
-1. Loader functions are pure relative to package resources and input args.
-2. No global mutable singleton required for unit tests.
-3. Caching is explicit and owned by startup composition.
-
-### Test and Validation Plan (Step 4 Scope)
-
-Unit tests:
-
-1. valid multi-skill registry load from packaged test fixtures
-2. duplicate id detection
-3. missing SKILL.md detection
-4. invalid frontmatter field constraints
-5. broken reference target detection
-6. invalid depends_on target detection
-7. cycle detection in depends_on graph
-8. deterministic output ordering across runs
-
-Packaging/runtime tests:
-
-1. install built wheel in isolated env
-2. load registry via `importlib.resources.files(...)`
-3. assert representative skill document/reference are readable
-
-Expected command path in this repo:
-
-1. `uv run pytest -q`
-
-### Acceptance Criteria for Step 4 Completion
-
-Step 4 is complete when all are true:
-
-1. Registry loads exclusively from packaged resources.
-2. All Step 2 and Step 3 dependent validations are enforced at startup.
-3. Invalid docs state blocks startup with actionable diagnostics.
-4. Registry is deterministic and immutable for runtime use.
-5. Catalog and later resource registration can consume registry without direct filesystem scanning.
-
-### Non-goals for Step 4
-
-1. No FastMCP resource registration wiring details (Step 5).
-2. No discovery-tool fallback behavior design (Step 6).
-3. No final packaging/build-system migration mechanics (Step 7).
-4. No backward-compat alias rollout mechanics in the greenfield baseline.
-5. No compatibility layer of any kind (URI aliases, dual reads, adapter shims, or legacy schema bridges).

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

@@ -1,221 +0,0 @@
-**Step 5 Results: Registry-Driven FastMCP Resource Registration (RFC6570 + Startup Safety)**
-
-This section finalizes Step 5 by defining how FastMCP resources are registered from the Step 4 docs registry using RFC6570 URI templates, explicit metadata, and strict duplicate-registration safety.
-
-### Greenfield Framing (Normative)
-
-This Step 5 design is for the greenfield target state:
-
-1. Registry-driven resources are the primary and authoritative discovery/read surface.
-2. No legacy per-skill hardcoded resource registration is retained.
-3. Resource contracts are defined for net-new clients and replace prior contracts without transition shims.
-4. Step 6 tool fallback layers on top of this resource contract, not as a competing source of truth.
-5. Breaking changes are intentional in this full-refactor phase.
-
-### Research Baseline (FastMCP + URI Templates)
-
-Authoritative references used for this step:
-
-1. FastMCP Resources and Templates docs (resource decorator, template behavior)
-2. FastMCP RFC6570 support docs (simple params, wildcard params, query params)
-3. FastMCP duplicate handling docs (`on_duplicate_resources`)
-4. FastMCP annotations guidance (`readOnlyHint`, `idempotentHint`)
-
-Best-practice conclusions applied to this design:
-
-1. Use URI templates for parameterized resources instead of generating N static resource handlers.
-2. Use wildcard template parameters (`{path*}`) for hierarchical docs paths.
-3. Set startup duplicate policy to `on_duplicate_resources="error"` to fail fast on contract collisions.
-4. Set explicit `mime_type` and resource annotations for all docs resources.
-5. Keep registration deterministic and sourced only from the validated Step 4 registry.
-
-### Registration Responsibilities (Normative)
-
-The Step 5 registration layer MUST:
-
-1. Consume only the validated in-memory registry produced by Step 4.
-2. Register canonical resource discovery surfaces and skill document/reference surfaces.
-3. Use RFC6570 templates where URI patterns are parameterized.
-4. Use wildcard templates where path depth is variable.
-5. Attach read-only/idempotent annotations to documentation resources.
-6. Set explicit MIME types for all registered resources.
-7. Fail startup if duplicate URI/template keys are encountered.
-
-### Canonical Resource Surface (from Registry)
-
-The preferred resources registered in this phase are:
-
-1. `resource://catalog/skills_index`
-2. `resource://catalog/skills_index{?q,tag,capability,cursor,limit}` (optional filtered/paginated discovery template)
-3. `resource://catalog/skills/{skill_id}`
-4. `resource://skills/{skill_id}/document`
-5. `resource://skills/{skill_id}/references/{ref_id}`
-6. `resource://docs/{path*}`
-
-Registration decision rules:
-
-1. Use static resource registration for fixed singleton endpoints (for example `skills_index`).
-2. Use template registration for parameterized endpoints (`{skill_id}`, `{ref_id}`) and optional discovery query templates.
-3. Use wildcard template registration for hierarchical docs routing (`{path*}`).
-4. Keep the singleton and query-template discovery surfaces semantically equivalent (same schema, query template adds filtering/pagination only).
-
-### Progressive Discovery Contract
-
-Discovery-first behavior for Step 5 resources:
-
-1. `skills_index` returns summaries only (no embedded full SKILL.md bodies).
-2. Each summary includes canonical follow-up URIs so clients can progressively fetch detail (`catalog/skills/{skill_id}` then `skills/{skill_id}/document`).
-3. Filtered/paginated discovery uses RFC6570 query params (`q`, `tag`, `capability`, `cursor`, `limit`) with deterministic ordering.
-4. Handlers should enforce bounded page size and return explicit continuation metadata when pagination is active.
-5. Errors for unsupported filter params or invalid cursor/limit are explicit and actionable.
-
-### RFC6570 Template Contract
-
-Path parameters:
-
-1. `{skill_id}` and `{ref_id}` are single-segment template params.
-2. `{path*}` is a wildcard param and may capture multi-segment paths separated by `/`.
-
-Validation contract at resource-read time:
-
-1. `skill_id` must exist in registry.
-2. `ref_id` must exist in that skill’s reference manifest.
-3. wildcard `path*` must normalize to an allowed docs-relative markdown path.
-4. invalid params return explicit not-found or validation errors (no silent fallback).
-
-Template function signature contract:
-
-1. Required URI params must exist as function parameters.
-2. Avoid hidden implicit params not represented in template.
-3. Keep template handlers side-effect free.
-
-### Metadata and Annotation Contract
-
-Each docs/resource registration should specify explicit metadata:
-
-1. `mime_type`
-   - skill docs and references: `text/markdown`
-   - catalog payloads: `application/json`
-2. `annotations`
-   - `readOnlyHint: true`
-   - `idempotentHint: true`
-3. `tags`
-   - include stable categories such as `catalog`, `skill-doc`, `reference`, `docs`
-4. `version`
-   - project-defined version from registry metadata where applicable
-5. `meta`
-   - include normalized identifiers (for example `skill_id`, `ref_id`, `source_relpath`) when useful
-
-### Startup Safety and Duplicate Policy
-
-FastMCP initialization contract for this phase:
-
-1. Construct the root server with `on_duplicate_resources="error"`.
-2. Register all Step 5 resources during startup composition before serving traffic.
-3. Treat duplicate registration as a hard startup failure.
-
-Duplicate conflict classes covered:
-
-1. static URI vs static URI collision
-2. static URI vs template key collision
-3. template URI vs template URI collision
-4. conflicting registrations introduced by future aliases without explicit migration handling
-
-### Registration Architecture
-
-Use one dedicated registration module that converts registry records into FastMCP resources.
-
-Recommended API:
-
-1. `register_docs_resources(mcp: FastMCP, registry: DocsRegistry) -> None`
-
-Responsibilities of `register_docs_resources`:
-
-1. register singleton catalog resources
-2. register parameterized catalog/detail templates
-3. register skill document and reference templates
-4. register docs wildcard template
-5. apply shared annotations and MIME defaults consistently
-
-Separation of concerns:
-
-1. Step 4 validates and normalizes docs state.
-2. Step 5 only registers handlers and reads from validated registry state.
-3. Request handlers do not re-discover filesystem/package structure.
-
-### Handler Behavior Contract
-
-Catalog handlers:
-
-1. `skills_index` returns compact deterministic discovery payload (summary records only) and supports progressive follow-up links.
-2. `skills/{skill_id}` returns one normalized detail record or not-found.
-
-Skill document handlers:
-
-1. `skills/{skill_id}/document` returns canonical SKILL markdown content.
-2. MIME type is always `text/markdown`.
-
-Reference handlers:
-
-1. `skills/{skill_id}/references/{ref_id}` resolves via frontmatter manifest mapping.
-2. MIME type is explicit from manifest or defaults to `text/markdown`.
-
-Wildcard docs handler:
-
-1. `docs/{path*}` serves markdown docs under canonical packaged docs tree.
-2. traversal outside docs root is blocked.
-
-### Integration Plan for Existing Modules
-
-Primary composition updates:
-
-1. Implement registry-driven registration in [src/personal_mcp/mcp.py](src/personal_mcp/mcp.py) as the canonical resource composition path.
-2. Keep [src/personal_mcp/main.py](src/personal_mcp/main.py) responsible for startup wiring order (load registry first, then register resources).
-3. Use [src/personal_mcp/catalog/server.py](src/personal_mcp/catalog/server.py) as registry-backed handlers only.
-
-Lifecycle order (required):
-
-1. load and validate registry (Step 4)
-2. initialize FastMCP with duplicate error policy
-3. register all Step 5 resources/templates
-4. start server
-
-### Testing Plan (Step 5 Scope)
-
-Unit/integration tests:
-
-1. resource registration succeeds with valid registry
-2. duplicate resource registration fails at startup
-3. `skills/{skill_id}` template resolves expected record
-4. `skills/{skill_id}/document` returns markdown with correct MIME
-5. `skills/{skill_id}/references/{ref_id}` resolves manifest-mapped file
-6. `docs/{path*}` resolves nested docs paths and blocks traversal attempts
-7. all registered docs resources include `readOnlyHint` and `idempotentHint`
-8. catalog payload order is deterministic
-9. filtered/paginated `skills_index{?q,tag,capability,cursor,limit}` responses are deterministic and schema-compatible with the singleton index response
-10. catalog index payload excludes full markdown bodies and includes follow-up URIs for progressive reads
-
-Smoke tests:
-
-1. list resources includes singleton and template entries
-2. read representative skill doc URI and reference URI successfully
-3. read representative wildcard docs URI successfully
-
-### Acceptance Criteria for Step 5 Completion
-
-Step 5 is complete when all are true:
-
-1. Resource registration is fully registry-driven (no per-skill hardcoded decorators required for core docs surfaces).
-2. RFC6570 templates are used for parameterized URI families, including wildcard where needed.
-3. All docs resources declare explicit MIME types and read-only/idempotent annotations.
-4. `on_duplicate_resources="error"` is enabled and verified by tests.
-5. Startup fails safely on registration conflicts.
-
-### Non-goals for Step 5
-
-1. No tool fallback discovery behavior implementation (Step 6).
-2. No packaging build inclusion mechanics (Step 7).
-3. No CI gate expansion details (Step 9).
-4. No migration shims for legacy URI aliases in the greenfield baseline.
-5. No ranking-strategy implementation for discovery tools beyond what is needed to preserve deterministic resource-first discovery contracts.
-6. No backward-compat resource aliases, adapter handlers, or dual registration paths.

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

@@ -1,243 +0,0 @@
-**Step 6 Results: Resource-First Discovery and Tool Fallback Contract**
-
-This section finalizes Step 6 by defining discovery behavior for clients that can attach MCP resources and the fallback behavior for clients or chat surfaces that must rely on MCP tools.
-
-### Step Deliverable
-
-- Update the current `docs/` directory with the finalized Step 6 discovery and fallback contract content from this document.
-
-### Primary Source Baseline (Repository Docs)
-
-Step 6 is based on the current project contracts in:
-
-1. `docs/architecture.md` (resource-first architecture and catalog role)
-2. `docs/usage.md` (operating flows, bounded loading, and fallback sequence)
-3. `docs/copilot.md` (client capability lanes and practical fallback behavior)
-4. `docs/mcp_layout.md` (shared content source and thin-tool fallback position)
-5. `docs/securing.md` (read-only/public-docs security invariant)
-
-Normative conclusions from those sources:
-
-1. Discovery stays resource-first.
-2. Tool fallback is allowed, thin, and read-only.
-3. Resources and tools must resolve to the same canonical authored markdown.
-4. Fallback behavior should keep context bounded and deterministic.
-
-### FastMCP Source Baseline (Authoritative References)
-
-Step 6 fallback behavior and compatibility-layer expectations align with:
-
-1. [FastMCP server concepts](https://gofastmcp.com/servers/server)
-2. [FastMCP resources and resource templates](https://gofastmcp.com/servers/resources)
-3. [FastMCP resources-as-tools transform](https://gofastmcp.com/servers/transforms/resources-as-tools)
-4. [MCP specification: resources](https://modelcontextprotocol.io/specification/latest/server/resources)
-
-Applied conclusions for this step:
-
-1. Resource contracts remain canonical and should be surfaced directly when clients support resource attachment.
-2. Tool-first compatibility layers should wrap canonical resource reads rather than creating alternate authored-content stores.
-3. URI-template-backed resource identity remains stable across direct-resource and tool-compatibility access paths.
-
-### Client Tool-Naming Research Baseline
-
-Authoritative and client-specific references to verify during implementation:
-
-1. [MCP specification: tools](https://modelcontextprotocol.io/specification/latest/server/tools)
-2. [MCP client concepts](https://modelcontextprotocol.io/docs/learn/client-concepts)
-3. [FastMCP tools](https://gofastmcp.com/servers/tools)
-4. [FastMCP resources-as-tools transform](https://gofastmcp.com/servers/transforms/resources-as-tools)
-5. [VS Code MCP servers](https://code.visualstudio.com/docs/agent-customization/mcp-servers)
-6. [VS Code MCP configuration reference](https://code.visualstudio.com/docs/agents/reference/mcp-configuration)
-7. [Cursor MCP documentation](https://docs.cursor.com/context/model-context-protocol)
-8. [Claude Desktop local MCP server setup](https://support.anthropic.com/en/articles/10949351-getting-started-with-local-mcp-servers-on-claude-desktop)
-
-Baseline naming conclusions:
-
-1. MCP protocol tool identity is the server-advertised `name` returned by `tools/list` and used in `tools/call`.
-2. FastMCP tool identity should be treated as the canonical server contract unless a tool is intentionally registered with an explicit alternate name.
-3. Clients and host integrations may display, namespace, or internally route tool names with provider-specific prefixes, but those wrappers are not canonical server tool names.
-4. Compatibility should be validated by observed `tools/list` and successful `tools/call` behavior in each target client rather than by assuming one global host naming convention.
-
-### Discovery Priority Contract (Normative)
-
-Preferred sequence for skill discovery and loading:
-
-1. `resource://catalog/skills_index`
-2. `resource://catalog/skills/{skill_id}`
-3. `resource://skills/{skill_id}/document`
-4. `resource://skills/{skill_id}/references/{ref_id}` only when needed
-
-Rules:
-
-1. Start from catalog discovery before loading any skill document.
-2. Do not skip straight to broad document loading when catalog metadata can narrow choices first.
-3. Use `resource://docs/{path*}` only for direct authored-doc access outside skill-specific flows.
-
-### Fallback Activation Rule
-
-Fallback is used only when the active client path cannot reliably attach MCP resources (for example, tool-only chat surfaces).
-
-Rules:
-
-1. Keep the same discovery order semantics as the resource path.
-2. If resource attachment is available, prefer resources over tools.
-3. Tool fallback must never become a second authoritative content source.
-
-### Tool Fallback Surface (Normative)
-
-The fallback tool surface includes:
-
-1. `list_resources`
-2. `read_resource`
-3. `search_patterns`
-4. `get_pattern_by_id`
-5. `get_skill_document_by_id`
-
-Canonical naming rule:
-
-1. The server-level tool contract uses the exact registered FastMCP tool names above.
-2. Clients that expose provider-prefixed names (for example, namespaced wrappers) must map those names to the canonical server tool name before invocation.
-3. `catalog_get_skill_document_by_id` is not a canonical server tool name for this contract unless an explicit alias is intentionally registered.
-
-Compatibility alias policy:
-
-1. Prefer canonical server tool names over aliases.
-2. Add server-side aliases only when a major client cannot reliably map its wrapper name back to the canonical name.
-3. Any alias must be read-only, delegate to the same payload builder as the canonical tool, and be documented as compatibility-only.
-4. If aliases are added, canonical and alias tools must return byte-for-byte equivalent payloads for the same input.
-
-Fallback order:
-
-1. call `list_resources` to inspect canonical static/template resource surfaces
-2. call `read_resource` for catalog URIs and selected skill URIs
-3. use thin catalog tools only when additional metadata-first narrowing is needed
-
-Tool behavior requirements:
-
-1. read-only and idempotent semantics
-2. deterministic ordering and bounded pagination
-3. explicit not-found responses (`found: false` style) where applicable
-4. payloads remain schema-aligned with catalog resources
-5. tool invocation examples and Copilot guidance must use canonical server tool names to avoid unknown-tool errors
-
-### Major Client Compatibility Plan
-
-Target clients and expected validation:
-
-1. GitHub Copilot in VS Code
-	- primary path: attach MCP resources when `MCP Resources...` is available
-	- fallback path: call `list_resources`, `read_resource`, then canonical thin tools only when needed
-	- validation: confirm Copilot-visible tool inventory includes or can invoke `list_resources`, `read_resource`, `search_patterns`, `get_pattern_by_id`, and `get_skill_document_by_id`
-	- compatibility risk: host-generated wrapper names may differ from canonical FastMCP names; document any observed wrapper-to-canonical mapping
-2. Cursor
-	- primary path: use the client MCP server configuration and resource/tool surfaces supported by the active Cursor version
-	- fallback path: prefer resource-backed tools first, then canonical thin tools
-	- validation: capture Cursor `tools/list` equivalent behavior and verify the canonical tool names or required host mappings
-	- compatibility risk: Cursor may present MCP tools through its own UI labels or internal routing names
-3. Claude Desktop
-	- primary path: configure the local MCP server and inspect advertised tools/resources in Claude Desktop
-	- fallback path: invoke canonical server tool names exactly as returned by `tools/list`
-	- validation: run a local smoke prompt that reads `resource://catalog/skills_index` and loads one skill document through `read_resource` or `get_skill_document_by_id`
-	- compatibility risk: local server configuration and transport setup may fail before tool-name compatibility is tested
-4. Generic MCP clients and SDK-based tests
-	- primary path: protocol-level `resources/list`, `resources/read`, `tools/list`, and `tools/call`
-	- fallback path: none beyond the canonical tool contract
-	- validation: automated smoke tests assert exact tool names returned by `tools/list` and successful calls for canonical names
-	- compatibility risk: SDK/client libraries may expose helper names that differ from raw protocol names
-
-Implementation checklist:
-
-1. Capture each target client's advertised tool names before adding aliases.
-2. Prefer fixing documentation or client-side mapping when the server already advertises canonical names correctly.
-3. Add a server-side alias only for a confirmed major-client incompatibility.
-4. Add regression tests for canonical names, resource-backed tools, and any intentionally supported aliases.
-5. Keep public examples centered on `list_resources`/`read_resource` and canonical thin tool names.
-
-### Resources-As-Tools Compatibility Layer
-
-Step 6 includes a resources-as-tools compatibility layer for clients that can call tools but not attach resources.
-
-Rules:
-
-1. It wraps canonical resource reads rather than re-implementing content transforms.
-2. It preserves canonical URIs and metadata semantics.
-3. It does not replace the minimal catalog tools listed above.
-4. It is interoperability-driven and remains read-only.
-
-### Resource/Tool Parity Contract
-
-Resources and fallback tools must agree on identity and routing metadata.
-
-Parity requirements:
-
-1. `skill_id` and `ref_id` are identical across both paths.
-2. canonical URIs in payloads match Step 3 URI rules.
-3. skill metadata (`id`, `name`, `description`, `tags`, `capabilities`, `version`) remains consistent.
-4. document payload returned by `get_skill_document_by_id` resolves to the same canonical `SKILL.md` content as `resource://skills/{skill_id}/document`.
-
-### Relevance and Ranking Contract
-
-Baseline matching behavior is metadata-first and deterministic.
-
-Rules:
-
-1. Search primarily over normalized skill metadata (id, name, description, tags).
-2. Keep deterministic ordering and deterministic pagination behavior.
-3. Keep ranking logic transparent and bounded for predictable client behavior.
-
-Optional extension policy:
-
-1. BM25/regex augmentation is allowed only when catalog/tool volume meaningfully harms token efficiency or precision.
-2. Any augmentation must preserve canonical ids, URIs, and deterministic tie-breaking.
-3. Any augmentation remains discovery-only and does not create alternate content payloads.
-
-### Context-Bounding and Clarification Policy
-
-To prevent context bloat and improve answer quality:
-
-1. load only the most relevant skill document by default
-2. load at most two skill documents in one pass unless the user explicitly asks for more
-3. if confidence is low after catalog discovery, ask one clarifying question before loading additional skill documents
-4. fetch references lazily and only when required
-
-### Security and Safety Constraints
-
-Fallback tools must preserve the project security invariant.
-
-Rules:
-
-1. tool surfaces stay documentation-only and read-only
-2. no mutation, shell execution, secret access, or private filesystem exposure
-3. all returned content remains safe to publish publicly
-
-### Integration Boundaries
-
-Step 6 integrates with prior steps as follows:
-
-1. Step 4 provides the validated in-memory registry.
-2. Step 5 provides canonical resource registration.
-3. Step 6 adds fallback discovery/read behavior that reuses the same registry and canonical markdown sources.
-
-Separation-of-concerns rule:
-
-1. Catalog/resource contracts remain canonical.
-2. Fallback tools are interoperability adapters, not a parallel architecture.
-
-### Acceptance Criteria for Step 6 Completion
-
-Step 6 is complete when all are true:
-
-1. Resource-first discovery remains the documented and implemented default path.
-2. `list_resources` and `read_resource` are available for tool-only clients.
-3. Thin catalog tools remain minimal, read-only parity surfaces.
-4. Fallback tool outputs map to canonical skill identities and URIs.
-5. Context loading is bounded and clarifying-question behavior is documented for low-confidence cases.
-6. No second content source is introduced; resources and tools resolve the same authored markdown.
-
-### Non-goals for Step 6
-
-1. No write or side-effecting tools.
-2. No alternate authored markdown stores or duplicated skill content pipelines.
-3. No guarantee that every client session exposes MCP resource attachment UI.
-4. No packaging/build contract changes (handled in Step 7).
-5. No CI gate expansion details (handled in later validation/governance steps).

.github/prompts/pytest-fill-scaffold.prompt.md

@@ -0,0 +1,69 @@
+---
+name: Pytest Fill Scaffold
+description: Fill scaffolded pytest test methods with assertions, fixtures, and minimal test data while preserving concise test names and one-line intent docstrings.
+argument-hint: Target test file(s) under tests plus stack (pure-python, fastapi, sqlalchemy-sync, sqlalchemy-async, or mixed)
+agent: agent
+---
+
+# Pytest Fill Scaffold
+
+Use this prompt after test scaffolding exists and method names/docstrings are already in place.
+
+## Inputs
+
+- Target test file(s) under `tests/`.
+- Stack type:
+  - `pure-python`
+  - `fastapi`
+  - `sqlalchemy-sync`
+  - `sqlalchemy-async`
+  - `mixed`
+- Optional constraints:
+  - keep implementation minimal vs comprehensive
+  - marker lane target (`unit`, `integration`, `smoke`)
+
+## Required References
+
+Load these in order and use only what matches the task:
+
+1. Core defaults: [pytest scaffolding skill](../../docs/skills/pytesting/SKILL.md)
+2. Naming/hierarchy preservation: [naming and organization](../../docs/skills/pytesting/references/naming-and-organization.md)
+3. Baseline pytest fixtures/markers: [pytest docs notes](../../docs/skills/pytesting/references/pytest-docs.md)
+4. FastAPI-specific behavior (only when needed): [fastapi testing](../../docs/skills/pytesting/references/fastapi-testing.md)
+5. SQLAlchemy-specific behavior (only when needed): [sqlalchemy testing](../../docs/skills/pytesting/references/sqlalchemy-testing.md)
+
+## Workflow
+
+1. Inspect target files and treat human-reviewed docstring-only scaffolds as invariant.
+2. Convert each scaffolded method into an executable test with a single behavior focus.
+3. Keep one-line docstrings for class and method intent.
+4. Add or refine fixtures at the nearest useful scope:
+   - global in `tests/conftest.py` only when broadly reusable
+   - subtree `conftest.py` for domain-specific fixtures
+5. Assign markers consistent with cost and dependencies:
+   - `unit` for pure logic
+   - `integration` for framework/DB contracts
+   - `smoke` for thin critical-path checks
+6. Validate in this order:
+   - `uv run pytest --collect-only -q`
+   - `uv run pytest -m unit -q` when unit tests are touched
+   - `uv run pytest -q` if dependencies are available
+
+## Authoring Rules
+
+- Prefer deterministic tests and explicit setup/teardown.
+- Keep assertions precise and readable.
+- Do not overfit tests to private implementation details.
+- If a scaffolded class or method has only a docstring body, treat its name and hierarchy as locked.
+- Do not rename, move, merge, split, or re-nest docstring-only scaffolded tests unless explicitly requested.
+- Preserve existing one-line docstrings on scaffolded classes and methods unless they are factually incorrect.
+- If stack details are missing and would change fixture strategy, ask one concise clarifying question before editing.
+
+## Output Format
+
+Return:
+1. Files updated.
+2. Fixture and marker decisions.
+3. Which references were used and why.
+4. Validation command results.
+5. Risks or open questions.

.github/prompts/pytest-scaffold.prompt.md

@@ -0,0 +1,72 @@
+---
+name: Pytest Scaffold
+description: Plan and scaffold pytest test files, class hierarchy, and concise method names for selected Python modules in this repository.
+argument-hint: Target module path(s) in src plus scope (plan-only or scaffold)
+agent: agent
+---
+
+# Pytest Scaffold
+
+Use this prompt to do in one run what we have been doing manually in chat:
+1. Build a naming and hierarchy plan for tests.
+2. Scaffold test files and class/method skeletons.
+3. Keep test method names concise because intent is carried by one-line docstrings.
+
+## Inputs
+
+- Target module path(s) under `src/`.
+- Scope mode:
+  - `plan-only`
+  - `scaffold`
+- Optional constraints:
+  - flattening preferences for path mapping under `tests/`
+  - method naming style preference
+
+## Repository Rules To Apply
+
+- Use [pytest scaffolding skill](../../docs/skills/pytesting/SKILL.md) for strategy and defaults.
+- Use [naming and organization reference](../../docs/skills/pytesting/references/naming-and-organization.md) before finalizing hierarchy.
+- Use `uv run pytest --collect-only -q` as structural validation.
+- Default to a source-mirror style adapted to this repository:
+  - map selected modules to `tests/` with concise path segments when requested
+  - keep one test module per source module
+
+## Execution Steps
+
+1. Inspect current `tests/` layout and identify existing naming patterns.
+2. Propose a concise hierarchy plan first:
+   - test file paths
+   - class hierarchy
+   - method naming pattern
+   - fixture placement (`tests/conftest.py` vs subtree `conftest.py`)
+3. If scope mode is `scaffold`, implement the skeleton:
+   - create missing test modules
+   - create class hierarchy
+   - add one-line docstrings to every class and test method
+   - keep test method names short and behavior-focused
+  - treat resulting docstring-only scaffolds as human-reviewed baseline for future fill-in work
+4. Validate collection with `uv run pytest --collect-only -q`.
+5. Report results:
+   - files created or updated
+   - collection outcome
+   - any ambiguities or follow-up choices
+
+## Class And Method Shape Defaults
+
+- Class shape:
+  - `Test<PrimarySubject>` as the top-level subject class
+  - nested `Test<MethodOrArea>` classes when it improves context
+  - top-level `Test<FunctionName>` classes for standalone module functions
+- Method shape:
+  - `test_<short_outcome>` naming
+  - one behavior target per method name
+  - one-line docstring that states the full intent
+
+## Output Format
+
+Return:
+1. Discovery summary and references consulted.
+2. Proposed or applied test tree.
+3. Class and method naming map.
+4. Validation command results.
+5. Open questions only if they block confident completion.

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

@@ -0,0 +1,183 @@
+## Goal
+
+Build a local, self-hosted documentation knowledge base that can ingest software docs, generate embeddings, store them in SQLite, and expose high-quality retrieval through MCP tools and resources.
+
+---
+
+## Core Architectural Decisions
+
+### Storage
+
+Use:
+
+* SQLite for metadata and document storage
+* FTS5 for keyword search
+* sqlite-vec for vector similarity search
+
+Avoid a separate vector database unless scale requirements emerge.
+
+---
+
+### Embeddings
+
+Use local embedding models via:
+
+* sentence-transformers
+
+Recommended model:
+
+```text
+BAAI/bge-base-en-v1.5
+```
+
+Store embeddings alongside document chunks.
+
+---
+
+### Ingestion
+
+Primary sources:
+
+1. Git repositories containing Markdown docs
+2. Documentation websites via Crawl4AI
+3. Sitemap-driven crawls when available
+
+Pipeline:
+
+```text
+Source
+  ↓
+Extract
+  ↓
+Normalize
+  ↓
+Chunk by headings
+  ↓
+Embed
+  ↓
+Store
+```
+
+Track content hashes so unchanged documents are skipped during reindexing.
+
+---
+
+### Retrieval
+
+Implement hybrid retrieval:
+
+```text
+FTS5 keyword search
+        +
+sqlite-vec similarity search
+        ↓
+Candidate set
+        ↓
+Reranker
+        ↓
+Final results
+```
+
+Reranker:
+
+```text
+BAAI/bge-reranker-v2
+```
+
+The retriever owns all ranking logic.
+
+---
+
+### Public Interface
+
+Do not expose vector search directly.
+
+Expose a retrieval service through MCP:
+
+```python
+search_docs(query)
+
+get_context(query)
+
+get_doc(path)
+```
+
+The MCP layer becomes the stable API.
+
+Clients never interact with embeddings or vectors.
+
+---
+
+## Repository Layout
+
+```text
+src/
+├── knowledge/
+│   ├── models.py
+│   ├── chunking.py
+│   ├── embeddings.py
+│   ├── ingestion.py
+│   ├── sqlite_store.py
+│   ├── hybrid_search.py
+│   ├── reranker.py
+│   └── retrieval.py
+│
+├── sources/
+│   ├── git_docs.py
+│   ├── crawl4ai_docs.py
+│   └── sitemap_docs.py
+│
+├── mcp_server/
+│   ├── tools.py
+│   └── resources.py
+│
+└── cli/
+    ├── ingest.py
+    └── reindex.py
+```
+
+---
+
+## Retrieval Flow
+
+```text
+User Query
+     ↓
+Embed Query
+     ↓
+FTS5 Search
+     +
+Vector Search
+     ↓
+Merge Results
+     ↓
+Rerank
+     ↓
+Return Context Bundle
+```
+
+Where a context bundle contains:
+
+```python
+ContextBundle(
+    passages=[...],
+    citations=[...],
+    related_docs=[...],
+)
+```
+
+---
+
+## Future Extensions
+
+Without changing the architecture:
+
+* Multiple documentation corpora
+* Version-aware retrieval
+* Code snippet indexing
+* MCP resources for specific topics
+* LangGraph integration
+* Docker deployment
+* Scheduled reindexing
+
+The key design principle is: **treat the vector store as an internal implementation detail and expose a retrieval-oriented MCP interface instead.**

docs

@@ -0,0 +1 @@
+src/personal_mcp/docs

docs/architecture.md

@@ -1,254 +0,0 @@
----
-icon: lucide/library
----
-
-# Architecture
-
-## Overview
-
-The platform is implemented as a resource-first MCP system with an integrated static documentation surface. The same methodology content powers both MCP resources and the published docs site.
-
-An MCP server is a runtime that exposes machine-readable resources and tools through stable interfaces so AI clients can discover and consume context consistently. Here, the server's role is intentionally narrow: publish canonical methodology documents as resources, keep discovery predictable through a catalog layer, and serve the same source material as pre-built static documentation.
-
-The system is complete in three layers:
-
-1. Canonical methodology is maintained in Markdown skill documents.
-2. Catalog resources provide normalized discovery.
-3. Zensical builds a static site from those same Markdown sources and the FastAPI app serves it in the FastMCP runtime process.
-
-Prompt documents under `docs/prompts/` are also indexed and exposed as first-class catalog and prompt surfaces.
-
-This architecture is anchored by three contracts:
-
-1. Docs-first authored content contract under `docs/` with strict per-skill ownership.
-2. Standard `SKILL.md` frontmatter consumed directly by FastMCP.
-3. Native `skill://` resource URIs with break-and-replace policy for contract changes.
-
-Detailed contract pages:
-
-1. [Content Contract](./contracts/index.md#content-contract)
-2. [Frontmatter Contract](./contracts/frontmatter.md)
-3. [URI Contract](./contracts/uris.md)
-
-This architecture keeps authored content human-friendly while preserving machine-stable contracts.
-
-## Intent
-
-The architecture is designed to satisfy three long-term requirements:
-
-1. Methodology must be editable as markdown by humans.
-2. Agents must consume stable, discoverable resource contracts, with a minimal read-only catalog tool fallback for constrained clients.
-3. Public documentation must be pre-built static output served from the application runtime without a separate docs service.
-
-## System Model
-
-### Pattern Modules
-
-Each skill encapsulates one methodology domain in a docs-owned directory:
-
-1. `docs/skills/<skill-id>/SKILL.md`
-2. `docs/skills/<skill-id>/references/...`
-
-The skill document and references are the authored source of truth; runtime code indexes and serves these files without becoming a second authored source.
-
-Each skill publishes three native resource families:
-
-1. `skill://<name>/SKILL.md` for primary instructions
-2. `skill://<name>/_manifest` for file discovery and integrity metadata
-3. `skill://<name>/{path*}` for supporting files
-
-The main resource returns canonical Markdown. The generated manifest lists real relative paths, sizes, and SHA256 hashes so clients can load supporting material selectively.
-
-### Prompt Modules
-
-Prompt guidance can be authored in `docs/prompts/` using either canonical prompt directories (`docs/prompts/<prompt-id>/PROMPT.md`) or legacy markdown files during migration.
-
-Prompt modules publish two additive surfaces:
-
-1. prompt resources for catalog and document retrieval
-2. MCP prompt objects for prompt-list/get-prompt style client workflows
-
-This keeps authored markdown as source-of-truth while allowing clients to discover and invoke prompts directly.
-
-### Catalog Module
-
-The catalog publishes normalized records for prompts. Skills use FastMCP's native resource discovery and client utilities instead of a parallel catalog.
-
-Typical catalog resources:
-
-1. resource://catalog/prompts_index
-2. resource://catalog/prompts_index{?q,tag,cursor,limit}
-3. resource://catalog/prompts/{prompt_id}
-
-Only canonical catalog resources are part of the runtime contract in this phase.
-
-### Registry Loader
-
-Importing the package does not read or parse documentation. The MCP server and FastAPI application factories initialize content when constructing a runnable server. The prompt/docs registry reads packaged resources through `importlib.resources.files(...)` and `Traversable` APIs; the native skills provider receives the packaged `personal_mcp/docs/skills` filesystem path.
-
-Loader responsibilities:
-
-1. Parse and validate prompt frontmatter.
-2. Build the prompt catalog and MCP prompt objects.
-3. Index authored Markdown for `resource://docs/{path*}`.
-
-Skill loading is owned by `SkillsDirectoryProvider`, which scans the packaged skills directory and constructs native resources before the server starts serving requests.
-
-The immutable registry is cached for the process lifetime. Each Uvicorn worker constructs and retains its own registry because worker processes do not share Python objects. Registry load failure is a server-factory startup error, not a package-import error or partial runtime warning.
-
-### Content Sources
-
-Content is authored in markdown under `docs/` and managed as long-form reference material. Skill documents and companion references now live under `docs/skills/`, while project-authored pages remain alongside them in the docs tree. Resource handlers expose the same authored documents through stable resource URIs.
-
-The repository root `docs/` directory is the only authored source. The `src/personal_mcp/docs` path is a relative symlink to that directory for source-checkout and editable-install workflows; it is not a second content tree and packaging does not depend on traversing it.
-
-For wheel builds, Hatchling's normal `src/personal_mcp` package traversal follows the relative `docs` symlink and archives its targets as regular files under `personal_mcp/docs/`. No `force-include` mapping is used because that would add the same archive paths twice. The prompt/docs registry uses [`importlib.resources.files`](https://docs.python.org/3/library/importlib.resources.html#importlib.resources.files), while `SkillsDirectoryProvider` scans the package-relative filesystem path. Neither path depends on the current working directory.
-
-### Static Docs Surface
-
-Static docs are built directly from two markdown source streams:
-
-1. Project-authored docs pages
-2. Skill and reference markdown pages
-
-The merged docs tree is built by Zensical into static files and served by the FastAPI app.
-
-Generated `site/` files are deployment assets for the human-facing static site. They are separate from the authored Markdown resources packaged under `personal_mcp/docs/`.
-
-## Data Flow
-
-```mermaid
-flowchart TD
-    A[Authored Skill Directories] --> B[SkillsDirectoryProvider]
-    B --> C[Native Skill Resources]
-    D[Authored Prompts and Docs] --> E[Prompt and Docs Registry]
-    E --> F[Prompt Catalog and Docs Resources]
-    A --> G[Zensical Static Build]
-    D --> G
-    G --> H[FastAPI Static Mount]
-```
-
-## Contracts
-
-### Metadata Contract
-
-Each skill declares standard frontmatter in `docs/skills/<skill-id>/SKILL.md`.
-
-For the full field-level contract, validation model, and FastMCP metadata mapping, see [Frontmatter Contract](./contracts/frontmatter.md).
-
-Required fields:
-
-1. name
-2. description
-
-The directory name is the provider identity and must match `name`. There is no skill catalog metadata or sidecar.
-
-### URI Contract
-
-Canonical resource URIs are:
-
-For the full URI semantics, parameter validation rules, and compatibility policy, see [URI Contract](./contracts/uris.md).
-
-1. skill://<skill_name>/SKILL.md
-2. skill://<skill_name>/_manifest
-3. skill://<skill_name>/<supporting_path>
-4. resource://docs/{path*}
-5. resource://catalog/prompts_index
-6. resource://catalog/prompts_index{?q,tag,cursor,limit}
-7. resource://catalog/prompts/{prompt_id}
-8. resource://prompts/{prompt_id}/document
-
-Validation rules:
-
-1. `skill_name` is the lowercase kebab-case skill directory name.
-2. `supporting_path` is a provider-validated relative path within that skill.
-3. Docs `path*` resolves only to normalized Markdown paths under `docs/`.
-
-### Resource Registration Contract
-
-Skill resources are registered by one `SkillsDirectoryProvider`; prompt and docs resources remain registered from the validated registry.
-
-Registration rules:
-
-1. Use RFC6570 URI templates where appropriate.
-2. Mark documentation resources as read-only and idempotent.
-3. Set explicit mime types for resource responses.
-4. Configure duplicate URI handling with `on_duplicate="error"` for startup safety.
-
-This keeps runtime behavior deterministic and prevents accidental URI collisions.
-
-### Versioning Rule
-
-URIs are unversioned and canonical in this phase.
-
-1. Breaking URI changes are handled as direct replacement.
-2. No compatibility aliases or dual URI families are maintained.
-
-## Static Hosting Pattern
-
-The docs site is pre-built and served by the same FastAPI runtime process used by the MCP app.
-
-Runtime behavior:
-
-1. App starts.
-2. FastAPI mounts the static docs output directory.
-3. Requests to docs paths are served as static assets.
-
-This provides a single deployment artifact with no runtime markdown rendering dependency.
-
-## Advantages
-
-### Single Source of Truth
-
-Methodology is authored once and reused in both MCP resources and docs pages.
-
-### High-Fidelity Agent Context
-
-Resources expose the same canonical Markdown that humans author and review.
-
-### Operational Simplicity
-
-A single app process serves MCP and docs surfaces.
-
-### Long-Term Maintainability
-
-Markdown remains easy to review, while contracts remain stable for clients.
-
-### Client Independence
-
-Clients can use Ask, Edit, or Agent modes without requiring prompt-first orchestration. Prompt objects are available as an additive MCP surface, while resource retrieval remains the canonical source path. MCP affordances are still chat-surface-dependent: some clients or sessions expose resource attachment directly, while others make tool invocation the more reliable retrieval path.
-
-## Authoring and Publishing Lifecycle
-
-1. Update markdown reference content.
-2. Keep skill `name` and directory identity aligned.
-3. Build static docs with Zensical and run provider tests.
-4. Package authored docs into `personal_mcp/docs/`.
-5. Serve native MCP resources and the static docs mount.
-
-## Scope and Non-Goals
-
-In-scope:
-
-1. Resource-first methodology delivery
-2. Native FastMCP skill discovery
-3. Pre-built static docs hosting in app runtime
-
-Out-of-scope:
-
-1. Prompt-first orchestration as the primary interface
-2. Large tool inventories duplicating static guidance across skill modules
-3. Separate dynamic docs service at runtime
-
-The prompt catalog remains an independent surface. Tool-only skill clients use generic resource tools rather than a skill-specific compatibility layer.
-
-## Example Content Inputs
-
-Existing markdown reference sets are valid examples of authored source material for this architecture:
-
-1. docs/skills/pytesting/references/pytest-docs.md
-2. docs/skills/python-logging/references/python-logging-docs.md
-3. docs/skills/python-logging/references/json-file-logging.md
-4. docs/skills/fastapi-uv-docker/references/fastapi-best-practices.md
-
-These inputs are treated as content sources, while native skill URIs and generated manifests form the machine-facing skill contract.

docs/contracts/prompt.md

@@ -1,75 +0,0 @@
----
-icon: lucide/messages-square
----
-
-# Prompt Contract
-
-This page defines the canonical contract for prompts in the docs-first MCP architecture.
-
-## Canonical Prompt Shape
-
-Each prompt is one directory under `docs/prompts/`:
-
-```mermaid
----
-config:
-    treeView:
-        rowIndent: 20
-        lineThickness: 2
-    themeVariables:
-        treeView:
-            labelColor: '#FFFFFF'
-            lineColor: '#FFFFFF'
----
-treeView-beta
-    "docs/"
-      "... (other docs)"
-      "prompts/"
-        "<prompt-id>/"
-          "PROMPT.md"
-          "references/"
-            "... (one or more markdown files, optional nested folders)"
-```
-
-Rules:
-
-1. `PROMPT.md` is required for every prompt.
-2. `references/` is the only place for prompt-specific supporting docs.
-3. Nested folders inside `references/` are allowed so a prompt can reorganize internals without changing global architecture.
-4. Prompt directories are independent ownership boundaries; no cross-prompt file writes.
-
-## Metadata Location Constraint
-
-1. Prompt metadata is embedded in YAML frontmatter in `PROMPT.md`.
-2. No `metadata.yaml` sidecar exists in the end state.
-3. Reference lookup metadata is documented and explicit: top-level `references/*.md` are auto-discovered from filenames, while `PROMPT.md` frontmatter declares overrides and nested mappings when needed.
-
-## Prompt Id Contract
-
-`prompt-id` is the public identifier and should satisfy all rules below:
-
-1. Format: lowercase kebab-case only.
-2. Character set: `a-z`, `0-9`, and `-`.
-3. Must start with a letter.
-4. No underscores, spaces, dots, or uppercase characters.
-5. Directory name should equal `prompt-id` in each committed revision.
-6. Frontmatter `id` should equal directory name in each committed revision.
-7. Treat `prompt-id` as immutable after release; any rename is a breaking replacement and clients must move to the new id.
-
-Valid examples:
-
-1. `pytest-fill-scaffold`
-2. `review-pr-comments`
-3. `scaffold-fastapi-service`
-
-Invalid examples:
-
-1. `fill_pytest_scaffold`
-2. `Prompt-Template`
-3. `docs.prompt`
-
-## Direct Documentation Inclusion
-
-1. For direct API documentation, use mkdocstrings directives rather than pasting large code blocks.
-2. Keep manually-authored code examples short and task-focused; large implementation excerpts are out of scope for this contract.
-

docs/mcp_layout.md

@@ -1,200 +0,0 @@
----
-icon: lucide/server
----
-
-# Static Docs Hosting Pattern
-
-## Purpose
-
-This document describes the completed layout and runtime pattern used to host a pre-built static documentation site from the same FastAPI app process that runs the FastMCP server.
-
-This design intentionally avoids runtime docs rendering and avoids a separate docs hosting service.
-
-It also treats Markdown as the single source of truth for both MCP resources and published docs.
-
-## Completed-State Layout
-
-```mermaid
----
-config:
-    treeView:
-        rowIndent: 40
-        lineThickness: 2
-    themeVariables:
-        treeView:
-            labelColor: '#FFFFFF'
-            lineColor: '#FFFFFF'
----
-treeView-beta
-   "project-root"
-      "pyproject.toml"
-      "uv.lock"
-      "zensical.toml"
-      "docs"
-         "index.md"
-         "<project-docs>.md"
-         "contracts"
-            "index.md"
-            "<contract-pages>.md"
-         "mcp_layout.md"
-         "prompts"
-            "<prompt-id>"
-               "PROMPT.md"
-               "references"
-         "skills"
-            "<skill-id>"
-               "SKILL.md"
-               "references"
-                  "<reference>.md"
-      "site"
-         "static build output"
-      "src"
-         "personal_mcp"
-            "__init__.py"
-            "main.py"
-            "mcp.py"
-            "catalog"
-               "<catalog-modules>.py"
-            "registry"
-               "<registry-modules>.py"
-            "web"
-               "<web-modules>.py"
-            "skills"
-               "<skills-modules>.py"
-```
-
-Notes:
-
-1. docs contains both project-authored pages and the canonical skill Markdown tree.
-2. site contains static build output only.
-3. docs/skills contains canonical skill Markdown and reference Markdown.
-4. docs/prompts contains canonical prompt Markdown used for prompt catalog and document surfaces.
-5. MCP resources and docs site read from the same Markdown sources.
-
-## Runtime Composition
-
-The runtime process serves two surfaces:
-
-1. MCP protocol surface from FastMCP
-2. Static docs surface from FastAPI static mount
-
-```mermaid
-flowchart TD
-   A[Packaged Skill Directory] --> B[SkillsDirectoryProvider]
-   C[Packaged Prompts and Docs] --> D[Validated Registry]
-   B --> E[FastMCP Server]
-   D --> E
-   E --> F[MCP Transport]
-   E --> G[FastAPI Application]
-   G --> H[Static Mount /docs]
-   H --> I[Zensical Site Output]
-```
-
-Runtime guarantees:
-
-1. The skills provider and prompt/docs registry initialize before resource exposure.
-2. Duplicate resource and template registration fails startup (`on_duplicate="error"`).
-3. Skill resources come directly from `SkillsDirectoryProvider` directory discovery.
-4. Legacy per-skill Python servers, custom skill catalogs, and metadata sidecars are not part of the runtime.
-
-## Build and Publish Flow
-
-The docs flow is pre-build only.
-
-1. Read authored docs pages and skill markdown sources.
-2. Build static site with Zensical into site.
-3. Start app and serve site directory as static files.
-
-No runtime markdown conversion is required.
-
-## Content Merge Pattern
-
-The published docs site always contains both:
-
-1. Project-authored docs pages
-2. Skill Markdown content from docs/skills/*/SKILL.md and references
-
-This ensures the public docs reflect architectural guidance and the exact Markdown served by MCP.
-
-## Markdown-to-Resource Mapping
-
-MCP resources map directly to canonical Markdown documents.
-
-Example mapping model:
-
-1. docs/skills/<skill-id>/SKILL.md -> skill://<skill-id>/SKILL.md
-2. docs/skills/<skill-id>/<path> -> skill://<skill-id>/<path>
-3. docs/<path>.md -> resource://docs/{path*}
-
-Catalog discovery resources are:
-
-1. resource://catalog/prompts_index
-2. resource://catalog/prompts_index{?q,tag,cursor,limit}
-3. resource://catalog/prompts/{prompt_id}
-
-Resource registration details:
-
-1. `skill://<skill-id>/SKILL.md` resolves to each skill's main instructions.
-2. `skill://<skill-id>/_manifest` lists every skill file with size and SHA256 hash.
-3. Per-skill wildcard templates resolve validated supporting-file paths.
-4. `resource://docs/{path*}` resolves normalized Markdown paths under `docs/`.
-
-When clients cannot attach MCP resources directly, `ResourcesAsTools` exposes generic `list_resources` and `read_resource` tools over the same provider resources.
-
-## URI Compatibility Policy
-
-1. Canonical URIs are the only supported URIs in this runtime.
-2. No backward-compatibility aliases or dual registration paths are maintained.
-3. Contract changes should update clients to canonical URIs directly.
-
-## Why This Pattern
-
-### Operational Simplicity
-
-One application process serves both protocol and static docs surfaces.
-
-### Deterministic Docs
-
-Published docs are immutable static assets for a given build.
-
-### Documentation Fidelity
-
-The docs site and MCP resources resolve from the same Markdown sources.
-
-### Maintainer Experience
-
-Authors continue to work in markdown while resource contracts remain machine-consumable.
-
-## FastAPI Static Mount Expectations
-
-The FastAPI app is expected to:
-
-1. Mount static directory containing Zensical output.
-2. Serve index and asset files from that directory.
-3. Keep docs route stable across releases.
-
-Recommended route conventions:
-
-1. /docs for static site root
-2. /docs/* for static assets and page routes
-
-## Update Lifecycle
-
-For each documentation update:
-
-1. Edit authored docs and skill markdown content.
-2. Rebuild static site.
-3. Restart runtime if needed.
-
-This keeps docs publication explicit and predictable.
-
-## Example Source Material
-
-Existing reference docs remain valid content inputs in this pattern:
-
-1. docs/skills/pytesting/references/pytest-docs.md
-2. docs/skills/python-logging/references/python-logging-docs.md
-3. docs/skills/python-logging/references/json-file-logging.md
-4. docs/skills/fastapi-uv-docker/references/fastapi-best-practices.md
-
-These are source documents, not deployment artifacts.

docs/skills/nicegui/references/architecture-and-styling.md

@@ -1,289 +0,0 @@
-# NiceGUI Page Layout And Styling
-
-Use this reference to structure NiceGUI pages, choose component boundaries, apply responsive layout, and introduce custom CSS without fighting Quasar's internal geometry.
-
-## Ownership And Dependency Boundaries
-
-Keep dependencies flowing in one direction:
-
-- pages import components and services
-- components contain presentation logic only
-- services contain business logic and do not import UI
-- bootstrap code mounts static assets and loads shared CSS once
-
-Suggested module split:
-
-```text
-src/my_app/
-  ui/
-    pages/
-    components/
-    static/
-  services/
-  api/
-```
-
-Page modules should compose a route from reusable presentation and service calls. They should not own domain rules, persistence, or long-running synchronous work.
-
-## Page Composition
-
-Build the outer layout before styling individual controls:
-
-1. Define the page shell and width constraints.
-2. Establish responsive rows, columns, gaps, and wrapping.
-3. Add semantic sections and repeated components.
-4. Configure Quasar component appearance with props.
-5. Add custom CSS only for behavior that props and utilities cannot express safely.
-
-```python
-with ui.column().classes("w-full max-w-6xl mx-auto gap-6 px-4"):
-    page_header(title="Inventory")
-
-    with ui.row().classes("w-full gap-4 flex-wrap lg:flex-nowrap items-start"):
-        filters_panel().classes("w-full lg:w-72 shrink-0")
-        item_grid().classes("w-full flex-1 min-w-0")
-```
-
-Use stable width, minimum-width, and flex constraints so labels, icons, validation messages, and loaded content do not shift the surrounding layout.
-
-## Component Extraction
-
-Extract a presentation pattern to `ui/components/` when it appears on two or more pages or when it owns a meaningful interaction boundary. Keep one-off route layout in the page module.
-
-```python
-def card_section(title: str, content: str) -> ui.card:
-    with ui.card().classes("w-full max-w-md") as card:
-        ui.label(title).classes("text-lg font-bold")
-        ui.label(content).classes("text-gray-600")
-    return card
-```
-
-Reusable components should accept data and event callbacks rather than import page state or business services implicitly.
-
-## Styling Decision Order
-
-NiceGUI wraps Quasar components. Choose the styling mechanism according to what it owns:
-
-1. Use Quasar props for component appearance, density, labels, and popup behavior.
-2. Use NiceGUI `.classes()` and Tailwind utilities for width, spacing, alignment, and responsive layout.
-3. Use reusable component functions for repeated visual patterns.
-4. Use `.style()` for genuinely dynamic inline values.
-5. Use minimal shared CSS only when props and utilities are insufficient.
-
-Common Quasar props include:
-
-- `outlined`
-- `dense`
-- `stack-label`
-- `popup-content-class`
-- `input-class`
-- `input-style`
-
-Avoid overriding internal selectors such as:
-
-- `.q-field__label`
-- `.q-field__native`
-- `.q-field__control`
-- `.q-field__input`
-
-Quasar coordinates field height, padding, labels, values, icons, and floating-label transforms. Changing only one internal part tends to cause clipping or overlap.
-
-## Responsive Layout
-
-Support these layouts only:
-
-- mobile: a single-column layout with wrapping toolbars and full-width controls
-- landscape desktop: $1920 \times 1080$ with side-by-side panels where they improve scanning
-- portrait desktop: $1080 \times 1920 with stacked panels or a narrow fixed sidebar
-
-Build the mobile layout first, then add one desktop breakpoint when a row or grid needs more space. Prefer flex wrapping and fluid grids before adding another breakpoint. Use Tailwind classes for page layout and Quasar props for component behavior.
-
-```python
-with ui.row().classes('w-full flex-wrap gap-4 lg:flex-nowrap items-start'):
-    filters_panel().classes('w-full lg:w-72 shrink-0')
-    item_grid().classes('w-full flex-1 min-w-0')
-```
-
-Use `min-w-0` for flexible children, `flex-wrap` for toolbars, and `max-w-* mx-auto` to keep portrait layouts readable. Do not add device-specific component trees, container queries, or custom breakpoints unless a supported layout demonstrates a concrete failure.
-
-## Static Assets And Shared CSS
-
-- Mount static assets from the composition layer.
-- Load shared CSS once rather than injecting it from individual pages.
-- Keep custom CSS tokenized with variables and scoped to application classes.
-- Avoid broad rules against Quasar internals.
-- Verify mount paths, reverse-proxy rewrites, and cache behavior.
-
-```python
-from pathlib import Path
-
-from fastapi.staticfiles import StaticFiles
-
-STATIC_DIR = Path(__file__).parent / "ui" / "static"
-
-app.mount("/static", StaticFiles(directory=STATIC_DIR), name="static")
-ui.add_css((STATIC_DIR / "css" / "base.css").read_text(encoding="utf-8"))
-```
-
-## Responsive Dialog Pattern
-
-Use whole-card scaling when a form dialog must become uniformly larger on mobile while preserving Quasar's internal proportions. Keep detached select menus unscaled and make the card itself scrollable.
-
-### Use Normal Field Density
-
-Normal Quasar fields are approximately `56px` high, while dense fields are approximately `40px` high. Remove `dense` when larger controls are needed.
-
-```python
-ui.input("Name").props("outlined")
-ui.number("Quantity").props("outlined")
-ui.select(...).props(
-    "outlined popup-content-class=app-item-detail-menu"
-)
-ui.textarea("Description").props("outlined autogrow")
-```
-
-Add a scoped class to the dialog card:
-
-```python
-ui.card().classes("app-detail-card app-item-detail-card")
-```
-
-### Scale The Complete Card
-
-```css
-:root {
-    --item-dialog-scale: 1;
-    --item-dialog-max-height: calc(100dvh - 3rem);
-}
-
-.app-item-detail-card {
-    width: min(50rem, 50vw);
-    max-height: var(--item-dialog-max-height);
-    overflow-y: auto;
-    overscroll-behavior: contain;
-    zoom: var(--item-dialog-scale);
-}
-
-/* Restore Quasar's baseline if a global rule overrides it. */
-.app-item-detail-card .q-field,
-.app-item-detail-menu {
-    font-size: 14px;
-}
-
-@media (max-width: 599px) {
-    :root {
-        --item-dialog-scale: 1.2;
-        /* 75dvh becomes 90dvh after 1.2x zoom. */
-        --item-dialog-max-height: 75dvh;
-    }
-
-    .app-item-detail-card {
-        width: 80vw;
-    }
-
-    .app-item-detail-menu {
-        font-size: 16.8px;
-    }
-}
-```
-
-The main mobile tuning knob is:
-
-```css
---item-dialog-scale: 1.2;
-```
-
-### Keep Detached Popups Unscaled
-
-Do not apply `zoom` or `transform: scale()` to a `QSelect` popup menu. Quasar renders menus outside the dialog and positions them from the unscaled anchor geometry. Scaling the menu container afterward separates it from its field.
-
-Avoid:
-
-```css
-.app-item-detail-card,
-.app-item-detail-menu {
-    zoom: 1.2;
-}
-```
-
-Use:
-
-```css
-.app-item-detail-card {
-    zoom: 1.2;
-}
-
-.app-item-detail-menu {
-    font-size: 16.8px;
-}
-```
-
-Use `popup-content-class=app-item-detail-menu` to target the detached menu and enlarge its text without changing its coordinate system.
-
-### Account For Zoom When Scrolling
-
-The card's pre-zoom maximum height must account for the scale:
-
-\[
-\begin{aligned}
-h_{\mathrm{pre}} &= \frac{h_{\mathrm{visible}}}{s} \\
-\text{where } s &= \text{the zoom scale}
-\end{aligned}
-\]
-
-For a desired visual height of `90dvh` at \(1.2\times\):
-
-\[
-\frac{90\,\mathrm{dvh}}{1.2} = 75\,\mathrm{dvh}
-\]
-
-Therefore:
-
-```css
---item-dialog-max-height: 75dvh;
-```
-
-Apply scrolling to the card itself:
-
-```css
-.app-item-detail-card {
-    max-height: var(--item-dialog-max-height);
-    overflow-y: auto;
-    overscroll-behavior: contain;
-}
-```
-
-This keeps the dimmed page stationary while the form scrolls.
-
-### Match The Quasar Breakpoint
-
-Quasar's extra-small breakpoint ends at `599.98px`. A mobile-only rule can use:
-
-```css
-@media (max-width: 599px) {
-    /* Mobile rules. */
-}
-```
-
-Confirm custom breakpoint values against the target application's Quasar configuration.
-
-## Validation Checklist
-
-Check each completed page at these three viewports:
-
-1. A representative mobile viewport, such as $390 \times 844$.
-2. Landscape desktop at $1920 \times 1080$.
-3. Portrait desktop at $1080 \times 1920$.
-
-Confirm that page sections do not overlap, toolbars wrap on mobile, desktop panels use the available space without becoming excessively wide, and dialogs remain visible and scroll to their final field.
-
-## Sources
-
-!!! info "Primary sources"
-    - [NiceGUI element styling and props](https://nicegui.io/documentation/element)
-    - [NiceGUI binding properties](https://nicegui.io/documentation/section_binding_properties)
-    - [Quasar components](https://quasar.dev/vue-components)
-    - [Quasar field](https://quasar.dev/vue-components/field/)
-    - [Quasar select](https://quasar.dev/vue-components/select/)
-    - [Tailwind responsive design](https://tailwindcss.com/docs/responsive-design)
-    - [MDN `zoom`](https://developer.mozilla.org/en-US/docs/Web/CSS/zoom)

pyproject.toml

@@ -1,17 +1,20 @@
 [project]
 name = "prompts"
-version = "0.1.0"
+version = "2.0.0"
 requires-python = ">=3.12"
 dependencies = [
-    "fastapi>=0.115.0",
-    "fastmcp>=3.4.4",
+    "fastapi>=0.133.0",
+    "fastmcp==4.0.0b1",
     "pydantic-settings>=2",
-    "python-json-logger>=4",
     "pyyaml>=6.0.2",
+    "python-json-logger>=4",
     "uvicorn[standard]>=0.34.0",
     "zensical>=0.0.45",
 ]
 
+[tool.uv]
+constraint-dependencies = ["fastmcp-slim==4.0.0b1"]
+
 [project.scripts]
 personal-mcp = "personal_mcp.main:main"
 
@@ -30,9 +33,11 @@ dev = [
     "ty>=0.0.51",
 ]
 test = [
+    "httpx2>=2.9.1",
     "pytest>=9.1.1",
     "pytest-asyncio>=1.4.0",
     "pytest-cov>=7.1.0",
+    "pyyaml>=6.0.2",
 ]
 
 [tool.pytest.ini_options]

src/personal_mcp/__main__.py

@@ -0,0 +1,19 @@
+import uvicorn
+
+from .config import get_settings
+
+
+def main(cli: bool = True) -> None:
+    """Run the root MCP server."""
+    settings = get_settings(cli=cli)
+    uvicorn.run(
+        "personal_mcp.web.app:create_app",
+        factory=True,
+        host=settings.host,
+        port=settings.port,
+        reload=settings.reload,
+    )
+
+
+if __name__ == "__main__":
+    main()

src/personal_mcp/catalog/__init__.py

@@ -1,11 +0,0 @@
-from personal_mcp.catalog.server import build_prompt_detail_payload
-from personal_mcp.catalog.server import build_prompts_index_payload
-from personal_mcp.catalog.server import get_prompt_by_id_payload
-from personal_mcp.catalog.server import search_prompts_payload
-
-__all__ = [
-    "build_prompt_detail_payload",
-    "build_prompts_index_payload",
-    "get_prompt_by_id_payload",
-    "search_prompts_payload",
-]

src/personal_mcp/catalog/server.py

@@ -1,125 +0,0 @@
-from __future__ import annotations
-
-from typing import Any
-
-from personal_mcp.registry.models.registry import DocsRegistry
-from personal_mcp.registry.models.registry import PromptRecord
-from personal_mcp.registry.models.registry import PromptSummaryPayload
-
-DEFAULT_LIMIT = 20
-MAX_LIMIT = 100
-
-
-def _prompt_matches(
-    prompt: PromptRecord,
-    *,
-    query: str | None,
-    tag: str | None,
-) -> bool:
-    if query:
-        lowered = query.strip().lower()
-        if lowered:
-            haystack = " ".join(
-                [
-                    prompt.prompt_id,
-                    prompt.name,
-                    prompt.description,
-                    " ".join(prompt.tags),
-                    " ".join(sorted(prompt.arguments)),
-                ]
-            ).lower()
-            terms = [term for term in lowered.replace("-", " ").split() if term]
-            if any(term not in haystack for term in terms):
-                return False
-
-    return not (tag and tag not in prompt.tags)
-
-
-def build_prompts_index_payload(
-    registry: DocsRegistry,
-    *,
-    query: str | None = None,
-    tag: str | None = None,
-    cursor: str | None = None,
-    limit: int | None = None,
-) -> dict[str, Any]:
-    normalized_limit = DEFAULT_LIMIT if limit is None else max(1, min(limit, MAX_LIMIT))
-    try:
-        start = 0 if cursor is None else max(0, int(cursor))
-    except ValueError as exc:
-        raise ValueError("cursor must be an integer string") from exc
-
-    ordered = [registry.prompts_by_id[prompt_id] for prompt_id in registry.prompts_in_load_order]
-    matches = [prompt for prompt in ordered if _prompt_matches(prompt, query=query, tag=tag)]
-
-    page = matches[start : start + normalized_limit]
-    next_cursor = start + normalized_limit
-
-    return {
-        "prompts": [PromptSummaryPayload.from_record(prompt).model_dump() for prompt in page],
-        "total": len(matches),
-        "cursor": str(start),
-        "limit": normalized_limit,
-        "next_cursor": str(next_cursor) if next_cursor < len(matches) else None,
-    }
-
-
-def build_prompt_detail_payload(registry: DocsRegistry, prompt_id: str) -> dict[str, Any]:
-    if prompt_id not in registry.prompts_by_id:
-        raise KeyError(prompt_id)
-
-    prompt = registry.prompts_by_id[prompt_id]
-    return {
-        "id": prompt.prompt_id,
-        "name": prompt.name,
-        "description": prompt.description,
-        "version": prompt.version,
-        "tags": list(prompt.tags),
-        "capabilities": list(prompt.capabilities),
-        "resources": {
-            "document": prompt.document_uri,
-        },
-        "arguments": {
-            arg_name: arg.model_dump(exclude_none=True) for arg_name, arg in sorted(prompt.arguments.items())
-        },
-    }
-
-
-def search_prompts_payload(
-    registry: DocsRegistry,
-    *,
-    query: str = "",
-    tags: list[str] | None = None,
-    skip: int = 0,
-    limit: int = DEFAULT_LIMIT,
-) -> dict[str, Any]:
-    normalized_skip = max(skip, 0)
-    normalized_limit = max(1, min(limit, MAX_LIMIT))
-
-    requested_tags = [tag.strip() for tag in (tags or []) if tag and tag.strip()]
-
-    matches: list[PromptRecord] = []
-    for prompt_id in registry.prompts_in_load_order:
-        prompt = registry.prompts_by_id[prompt_id]
-        if not _prompt_matches(prompt, query=query, tag=None):
-            continue
-        if requested_tags and any(tag not in prompt.tags for tag in requested_tags):
-            continue
-        matches.append(prompt)
-
-    page = matches[normalized_skip : normalized_skip + normalized_limit]
-    return {
-        "prompts": [PromptSummaryPayload.from_record(prompt).model_dump() for prompt in page],
-        "total": len(matches),
-        "skip": normalized_skip,
-        "limit": normalized_limit,
-    }
-
-
-def get_prompt_by_id_payload(registry: DocsRegistry, prompt_id: str) -> dict[str, Any]:
-    if prompt_id not in registry.prompts_by_id:
-        return {"found": False, "id": prompt_id}
-    return {
-        "found": True,
-        "prompt": build_prompt_detail_payload(registry, prompt_id),
-    }

src/personal_mcp/config.py

@@ -1,6 +1,5 @@
 from functools import cache
 from pathlib import Path
-from typing import Literal
 
 from pydantic import BaseModel
 from pydantic import DirectoryPath
@@ -9,7 +8,7 @@ from pydantic_settings import BaseSettings
 from pydantic_settings import SettingsConfigDict
 
 DEFAULT_ENV_FILE = Path(".env").resolve()
-_REPO_ROOT = Path(__file__).resolve().parents[2]
+DEFAULT_SITE_DIR = Path("site").resolve()
 
 
 class Mounts(BaseModel):
@@ -24,18 +23,21 @@ class Settings(BaseSettings):
         env_file=DEFAULT_ENV_FILE,
         env_prefix="PERSONAL_MCP_",
         extra="ignore",
+        cli_implicit_flags=True,
     )
 
     debug: bool = False
     log_level: str = "info"
     mounts: Mounts = Field(default_factory=Mounts)
-    mcp_transport: Literal["http", "sse"] = "http"
-    site_dir: DirectoryPath = Field(default=_REPO_ROOT / "site")
+    site_dir: DirectoryPath = Field(default=DEFAULT_SITE_DIR)
+    host: str = "localhost"
+    port: int = 8080
+    reload: bool = True
 
 
 @cache
-def get_settings(**overrides) -> Settings:
-    return Settings(**overrides)
+def get_settings(*, cli: bool = False, **overrides) -> Settings:
+    return Settings(**overrides, _cli_parse_args=cli)  # pyright: ignore[reportCallIssue]
 
 
 def refresh_settings(**overrides):

src/personal_mcp/docs

@@ -1 +0,0 @@
-../../docs

src/personal_mcp/docs/architecture.md

@@ -0,0 +1,105 @@
+---
+icon: lucide/library
+---
+
+# Architecture
+
+## Overview
+
+The application combines a FastMCP server with a pre-built Zensical documentation site. Markdown under `docs/` is the single authored content tree, while native FastMCP providers own skill and prompt discovery.
+
+The runtime has four content paths:
+
+1. `SkillsDirectoryProvider` publishes native `skill://` resources from packaged skill directories.
+2. A custom prompt provider loads declarative prompt definitions from packaged Markdown.
+3. The general docs registry publishes non-skill Markdown through `resource://docs/{path*}`.
+4. FastAPI serves the pre-built `site/` directory.
+
+There is no custom skill catalog, prompt catalog, or per-prompt Python module.
+
+## Source Ownership
+
+### Skills
+
+Each skill owns one directory:
+
+1. `docs/skills/<skill-id>/SKILL.md`
+2. `docs/skills/<skill-id>/<supporting-path>`
+
+`SkillsDirectoryProvider` publishes:
+
+1. `skill://<name>/SKILL.md`
+2. `skill://<name>/_manifest`
+3. `skill://<name>/{path*}`
+
+The provider parses standard skill frontmatter and generates the manifest. The general docs registry excludes `skills/**`, so only the native provider owns this namespace.
+
+### Prompts
+
+Each prompt has one source: `docs/prompts/<prompt-id>/PROMPT.md`. Its nested `prompt` frontmatter owns runtime metadata and argument declarations, while its body owns canonical prose.
+
+The custom provider reads packaged Markdown with `importlib.resources`, validates metadata and exact placeholder-to-argument equality, and creates native FastMCP prompt objects. It rescans on each list and get request, so an editable deployment observes file additions, edits, and deletions without a restart.
+
+FastMCP exposes prompts through native `prompts/list` and `prompts/get` operations.
+
+### General Docs
+
+The docs registry indexes packaged Markdown for `resource://docs/{path*}`. It rejects `skills/**` because skills are provider-owned. Prompt Markdown can remain visible as general documentation, but prompt invocation is owned by the native prompt provider.
+
+## Runtime Composition
+
+```mermaid
+flowchart TD
+    A[Packaged Skill Directories] --> B[SkillsDirectoryProvider]
+    C[Packaged Prompt Markdown] --> D[Markdown Prompt Provider]
+    F[General Markdown] --> G[Docs Registry]
+    B --> H[FastMCP Server]
+    D --> H
+    G --> H
+    H --> K[MCP Transport]
+    L[Zensical Site Output] --> M[FastAPI Static Mount]
+    K --> M
+```
+
+Server construction is lazy with respect to package import. Each application process creates its providers and docs snapshot when the server factory runs. Skills use startup discovery, while prompts are reloaded when a client lists or gets prompts.
+
+## Packaging
+
+The repository root `docs/` directory is the only authored Markdown source. `src/personal_mcp/docs` is a relative symlink used by source checkouts and editable installs. Hatchling follows it and stores regular files beneath `personal_mcp/docs/` in the wheel.
+
+Runtime reads are package-relative:
+
+1. Prompt content and general docs use `importlib.resources` and `Traversable` APIs.
+2. `SkillsDirectoryProvider` receives the packaged `personal_mcp/docs/skills` filesystem path.
+3. No runtime content lookup depends on the current working directory.
+
+## Public Contracts
+
+The machine-facing surfaces are:
+
+1. Native skill resources under `skill://<name>/...`.
+2. Native MCP prompt list and get operations.
+3. `resource://docs/{path*}` for general Markdown.
+
+Canonical contracts are documented in:
+
+1. [Prompt Contract](./contracts/prompt.md)
+2. [Skill Contract](./contracts/skill_contract.md)
+3. [Frontmatter Contract](./contracts/frontmatter.md)
+4. [URI Contract](./contracts/uris.md)
+
+Only these canonical provider and protocol surfaces are registered.
+
+## Static Documentation
+
+Zensical builds `docs/` into `site/` before deployment. FastAPI mounts that immutable output in the same process that hosts FastMCP. Generated `site/` files are deployment assets and are never an authored source.
+
+## Validation
+
+Changes are accepted only after:
+
+1. focused provider and protocol tests
+2. Ruff and ty checks
+3. a Zensical build
+4. the full pytest suite
+5. an installed-wheel smoke test when packaging or provider paths change

src/personal_mcp/docs/authoring.md

@@ -72,22 +72,23 @@ Recommended sequence:
 
 ## Prompt Authoring
 
-Prompts remain registry-backed:
+A prompt is one self-describing `docs/prompts/<prompt-id>/PROMPT.md` file:
 
-1. Keep one canonical `PROMPT.md`.
-2. Align directory name, `name`, and `x-personal-mcp.id`.
-3. Include `resource://prompts/<prompt-id>/document` in capabilities.
-4. Define arguments beneath `x-personal-mcp.arguments`.
-5. Keep long rationale and sources in `references/`.
+1. Create a lowercase kebab-case directory beneath `docs/prompts/`.
+2. Add a nested `prompt` frontmatter mapping with version, description, tags, and ordered arguments.
+3. Give every argument a description and explicit required flag.
+4. Add `choices` only when a string argument accepts a fixed set of values.
+5. Use each argument exactly once or more as a `{{argument_name}}` placeholder in the body.
+6. Do not add a Python component, name field, metadata sidecar, or central catalog entry.
 
-Prompt argument names must be valid Python identifiers. Each argument accepts optional `title`, `description`, and `required`; unknown fields fail strict validation.
+The custom provider rescans prompt documents during every native list and get request. Changes in an editable checkout are therefore visible on the next request without a process restart. Invalid metadata or placeholder drift fails that request with a configuration error.
 
 ## Frontmatter Safety
 
 1. Quote scalar values containing `:`.
 2. Quote values with reserved YAML characters such as `#`, `{}`, `[]`, or leading `*`.
 3. Use block scalars for punctuation-heavy multiline text.
-4. Keep fields within the applicable skill or prompt contract.
+4. Keep fields within the applicable skill or documentation contract.
 
 ## Writing Quality
 
@@ -106,7 +107,7 @@ Active instructions should point directly to native main resources:
 2. `skill://pytesting/SKILL.md`
 3. `skill://vscode-configuration/SKILL.md`
 
-When deeper guidance is needed, read the selected skill's `_manifest` and fetch supporting files by their listed path. Tool-only clients use `list_resources` and `read_resource` over the same URIs.
+When deeper guidance is needed, read the selected skill's `_manifest` and fetch supporting files by their listed path.
 
 ## Validation Checklist
 

src/personal_mcp/docs/contracts/frontmatter.md

@@ -4,7 +4,7 @@ icon: lucide/braces
 
 # Frontmatter Contract
 
-This page defines the authored frontmatter contracts for native FastMCP skills and registry-backed prompts.
+This page defines frontmatter ownership for native skills and prompt documentation.
 
 ## Skill Frontmatter
 
@@ -27,38 +27,30 @@ Rules:
 
 The provider uses the directory name as the URI identity and the frontmatter `description` as the main resource description. Repository tests enforce directory/name parity and reject extra skill frontmatter fields.
 
-## Prompt Frontmatter
+## Prompt Documentation Frontmatter
 
-Prompts remain registry-backed and retain repository metadata:
+Each prompt stores runtime metadata in a nested `prompt` mapping beside fields consumed by the static documentation site. The runtime mapping uses this shape:
 
 ```yaml
 ---
-name: <prompt-id>
-description: <what the prompt does and when to use it>
-x-personal-mcp:
-  id: <prompt-id>
-  version: <semver>
-  tags:
-    - <tag>
-  capabilities:
-    - resource://prompts/<prompt-id>/document
-  arguments:
-    <argument-name>:
-      title: <display title>
-      description: <input guidance>
-      required: true
+icon: lucide/messages-square
+prompt:
+ version: "1.0.0"
+ description: Describe when to use the prompt.
+ tags: [example, prompts]
+ arguments: {topic: {description: "Topic to process.", required: true, choices: [first, second]}, notes: {description: "Optional constraints.", required: false}}
 ---
 ```
 
 Prompt rules:
 
-1. `name`, `description`, and `x-personal-mcp` are required.
-2. `x-personal-mcp.id`, `name`, and the prompt directory name must match.
-3. `version` must be semantic version text.
-4. `capabilities` must include `resource://prompts/<prompt-id>/document`.
-5. Argument names must be valid Python identifiers.
-6. Argument entries accept optional `title`, `description`, and `required` fields.
-7. Unknown prompt fields are rejected by the strict Pydantic registry models.
+1. `version`, `description`, `tags`, and `arguments` are required; unknown fields inside `prompt` or an argument are rejected.
+2. The directory name supplies the prompt id. Do not add a duplicate `name` field.
+3. Argument names must be valid identifiers and preserve their authored mapping order.
+4. Every argument requires a non-empty `description` and explicit `required` boolean.
+5. Optional `choices` must be a non-empty list of unique, non-empty strings.
+6. Markdown placeholders must exactly match the declared argument names.
+7. Top-level fields such as `icon` remain owned by the documentation site and are not runtime prompt metadata.
 
 See the MCP [prompts concept documentation](https://modelcontextprotocol.io/docs/learn/server-concepts#prompts) and [schema reference](https://modelcontextprotocol.io/specification/latest/schema) for the protocol-level prompt shape.
 
@@ -70,11 +62,11 @@ Skill validation is file- and provider-oriented:
 2. FastMCP parses the description and scans all files when the provider is created.
 3. Repository tests enforce the stricter standard-only frontmatter and directory/name rules.
 
-Prompt validation remains registry-oriented and fails server startup for invalid metadata, duplicate prompt ids, or malformed arguments.
+Prompt validation is provider- and renderer-oriented. Every list or get request reloads and validates the authored files. A malformed definition fails the request instead of publishing a partial prompt set.
 
 ## Invariants
 
 1. Skills remain directly portable to tools that understand standard Agent Skills directories.
 2. Native skill discovery has no parallel catalog metadata source.
-3. Prompts retain the richer metadata required by their catalog and MCP prompt-object surfaces.
+3. Prompts use FastMCP's native component metadata and protocol surface without a parallel catalog or Python component file.
 4. All authored content remains under `docs/`.

src/personal_mcp/docs/contracts/prompt.md

@@ -0,0 +1,84 @@
+---
+icon: lucide/messages-square
+---
+
+# Prompt Contract
+
+This page defines the canonical contract for declarative prompts published through a custom [FastMCP provider](https://gofastmcp.com/servers/providers/custom).
+
+## Canonical Prompt Shape
+
+Each prompt is one self-describing Markdown document:
+
+```mermaid
+---
+config:
+    treeView:
+        rowIndent: 20
+        lineThickness: 2
+    themeVariables:
+        treeView:
+            labelColor: '#FFFFFF'
+            lineColor: '#FFFFFF'
+---
+treeView-beta
+    "docs/prompts/"
+      "<prompt-id>/"
+        "PROMPT.md"
+    "src/personal_mcp/prompts/"
+      "content.py"
+      "models.py"
+      "provider.py"
+```
+
+Rules:
+
+1. The parent directory name defines the public prompt id.
+2. The nested `prompt` frontmatter block defines version, description, tags, and arguments.
+3. Argument declarations define names, descriptions, requiredness, and optional string choices.
+4. The Markdown body owns the rendered prompt prose and uses `{{argument_name}}` placeholders.
+5. Declared arguments and body placeholders must match exactly.
+6. No Python file is added when authoring a prompt.
+
+## Ownership Boundary
+
+1. Each `PROMPT.md` owns both its runtime metadata and prose.
+2. Python owns only generic parsing, validation, rendering, and provider behavior.
+3. There is no central prompt catalog, generated signature, or metadata sidecar.
+4. The provider scans direct children of packaged `docs/prompts/` on each list or get request.
+5. Additions, edits, and deletions become visible on the next request without restarting the server.
+6. Reload is pull-based; the provider does not watch files or emit proactive change notifications.
+
+## Prompt Id Contract
+
+`prompt-id` is the public identifier and should satisfy all rules below:
+
+1. Format: lowercase kebab-case only.
+2. Character set: `a-z`, `0-9`, and `-`.
+3. Must start with a letter.
+4. No underscores, spaces, dots, or uppercase characters.
+5. Directory name should equal `prompt-id` in each committed revision.
+6. The provider derives the prompt name from the directory; frontmatter must not duplicate it.
+7. Treat `prompt-id` as immutable after release; a rename is a breaking replacement.
+
+Valid examples:
+
+1. `pytest-fill-scaffold`
+2. `review-pr-comments`
+3. `scaffold-fastapi-service`
+
+Invalid examples:
+
+1. `fill_pytest_scaffold`
+2. `Prompt-Template`
+3. `docs.prompt`
+
+## Rendering Contract
+
+1. The loader requires one leading YAML frontmatter block and validates its nested `prompt` mapping strictly.
+2. All MCP arguments are strings; `choices` optionally restricts accepted values.
+3. Missing required arguments, unknown arguments, and invalid choices fail before rendering.
+4. An omitted optional value renders as `Not provided`.
+5. Unknown prompt ids, malformed metadata, and mismatched placeholders fail immediately.
+6. Prompt content is read through [importlib resources](https://docs.python.org/3/library/importlib.resources.html) and does not depend on the working directory.
+

src/personal_mcp/docs/contracts/uris.md

@@ -4,7 +4,7 @@ icon: lucide/link
 
 # URI Contract
 
-This page defines the public resource URI contract for native skills, registry-backed prompts, and general authored documentation.
+This page defines the public resource URI contract for native skills and general authored documentation.
 
 ## Native Skill URIs
 
@@ -44,17 +44,11 @@ skill://pytesting/references/pytest-docs.md
 
 FastMCP confines reads to the selected skill directory. Absolute paths, traversal outside the directory, missing files, directories, and symlinks that resolve outside the skill root are rejected.
 
-## Prompt And Docs URIs
+## General Docs URI
 
-Prompts and general documentation retain the existing registry-backed resource surface:
+General authored documentation is exposed through `resource://docs/{path*}`. The wildcard accepts normalized relative POSIX Markdown paths beneath `docs/`, excludes the provider-owned `skills/` subtree, and rejects absolute paths, traversal segments, backslashes, and non-Markdown targets.
 
-1. `resource://catalog/prompts_index`
-2. `resource://catalog/prompts_index{?q,tag,cursor,limit}`
-3. `resource://catalog/prompts/{prompt_id}`
-4. `resource://prompts/{prompt_id}/document`
-5. `resource://docs/{path*}`
-
-Prompt ids remain lowercase kebab-case. The docs wildcard accepts normalized relative POSIX Markdown paths beneath `docs/` and rejects absolute paths, traversal segments, backslashes, and non-Markdown targets.
+Prompts are MCP prompt components rather than resources. Clients discover them with the protocol `prompts/list` operation and render them with `prompts/get`.
 
 ## Discovery Order
 
@@ -66,11 +60,11 @@ For skills:
 4. read `_manifest` when supporting material may be needed
 5. fetch only the supporting paths relevant to the task
 
-For prompts, use the prompt catalog or MCP prompt-object APIs.
+For prompts, use the native MCP prompt APIs or their generic tool projection.
 
-## Compatibility Policy
+## Stability Policy
 
-The native `skill://` family directly replaces the repository's former custom skill URI and catalog surfaces. No compatibility aliases or dual registrations are maintained. Prompt and general-doc URIs are unaffected.
+The provider and protocol surfaces documented here are the complete public contract. Contract changes replace the affected surface directly.
 
 Skill renames are breaking because the directory name is part of every native skill URI. Supporting-file renames change the corresponding manifest path and URI.
 
@@ -80,3 +74,4 @@ Skill renames are breaking because the directory name is part of every native sk
 2. [MCP resources](https://modelcontextprotocol.io/specification/latest/server/resources)
 3. [RFC 3986 URI syntax](https://www.rfc-editor.org/rfc/rfc3986)
 4. [RFC 6570 URI templates](https://www.rfc-editor.org/rfc/rfc6570)
+5. [FastMCP prompts](https://gofastmcp.com/servers/prompts)

src/personal_mcp/docs/copilot.md

@@ -6,7 +6,7 @@ icon: lucide/bot
 
 ## Purpose
 
-This page explains how GitHub Copilot in VS Code consumes native skill resources from `personal-mcp`, including sessions where tools are visible but resource attachment is not.
+This page explains how GitHub Copilot in VS Code consumes native skill resources and prompts from `personal-mcp`.
 
 ## Capability Lanes
 
@@ -16,7 +16,7 @@ Copilot interacts with MCP servers through independently exposed lanes:
 2. resources attached as read-only context
 3. server-provided prompts
 
-This server publishes skills as native `skill://` resources, prompts through registry-backed resources and MCP prompt objects, and generic resource fallback tools through FastMCP.
+This server publishes skills as native `skill://` resources and prompts as native MCP prompt objects.
 
 ## Native Skill Resources
 
@@ -39,22 +39,11 @@ A successful `resources/list` response does not guarantee the picker appears in
 
 ## Recommended Workflow
 
-When resource attachment is available:
-
 1. browse the server's resources
 2. attach one relevant `skill://<name>/SKILL.md`
 3. attach `_manifest` only if supporting detail may be needed
 4. attach only selected supporting files
 
-When only tools are available:
-
-1. call `list_resources`
-2. select a native main skill URI by name and description
-3. call `read_resource` for that URI
-4. read `_manifest` and supporting files only as needed
-
-Both paths resolve through the same FastMCP provider.
-
 ## Prompt Examples
 
 Resource attachment:
@@ -63,12 +52,6 @@ Resource attachment:
 Use the attached personal-mcp skill as guidance, then reconcile it with the repository before proposing changes.
 ```
 
-Tool-only discovery:
-
-```text
-Call list_resources, choose the best matching skill://.../SKILL.md resource, and read it. Inspect its _manifest only if a supporting file is needed. Load at most two candidate skills.
-```
-
 Direct loading:
 
 ```text
@@ -89,7 +72,7 @@ A repo-level instruction should name the native retrieval order and context budg
 When a task matches a personal-mcp skill:
 
 1. Prefer an already attached native skill resource.
-2. Otherwise use `list_resources` and select one `skill://<name>/SKILL.md` resource by description.
+2. Otherwise browse MCP resources and select one `skill://<name>/SKILL.md` resource by description.
 3. Read `_manifest` only when supporting material is needed.
 4. Load at most two candidate main files and only the relevant supporting paths.
 5. Reconcile guidance with the current repository before editing.
@@ -99,7 +82,7 @@ Instructions steer behavior but do not force VS Code to attach resources automat
 
 ## Prompt Objects
 
-Prompt modules remain separate from skills. When the client supports MCP prompt APIs, use prompt listing and `get_prompt` for parameterized workflows. Authored `PROMPT.md` remains the source of truth for each prompt.
+Prompts remain separate from skills. When the client supports MCP prompt APIs, use prompt listing and `get_prompt` for parameterized workflows. Each authored `PROMPT.md` is the complete source of truth for its metadata, arguments, and prose; changes are loaded on the next prompt request.
 
 ## Troubleshooting
 
@@ -107,7 +90,6 @@ Prompt modules remain separate from skills. When the client supports MCP prompt
 2. Use `MCP: Browse Resources` to confirm native skill resources exist.
 3. Restart the MCP server after changing skill files because production uses `reload=False`.
 4. Reload the VS Code window if the server is healthy but the resource picker remains stale.
-5. In tool-only sessions, verify `list_resources` and `read_resource` are visible.
 
 ## Further Reading
 

src/personal_mcp/docs/mcp_layout.md

@@ -0,0 +1,95 @@
+---
+icon: lucide/server
+---
+
+# Runtime And Static Docs Layout
+
+## Purpose
+
+The project serves native MCP content and a pre-built documentation site from one FastAPI process. Markdown is authored once under `docs/`; runtime providers and Zensical consume that same packaged tree for different purposes.
+
+## Repository Layout
+
+```mermaid
+---
+config:
+    treeView:
+        rowIndent: 32
+        lineThickness: 2
+---
+treeView-beta
+   "project-root"
+      "docs"
+         "prompts/<prompt-id>/PROMPT.md"
+         "skills/<skill-id>/SKILL.md"
+         "skills/<skill-id>/<supporting-files>"
+         "<general-pages>.md"
+      "site"
+         "static build output"
+      "src/personal_mcp"
+         "mcp.py"
+         "prompts/content.py"
+         "prompts/models.py"
+         "prompts/provider.py"
+         "registry/"
+         "skills/provider.py"
+         "web/"
+```
+
+Ownership rules:
+
+1. `docs/skills/` is owned exclusively by `SkillsDirectoryProvider` at runtime.
+2. Each file under `docs/prompts/` owns its prompt metadata, argument schema, and prose.
+3. The docs registry owns only general Markdown resources and explicitly excludes skills.
+4. `site/` is generated output.
+5. The deleted custom `catalog/` package is not part of the runtime.
+
+## Runtime Composition
+
+```mermaid
+flowchart TD
+   A[Packaged Skills] --> B[SkillsDirectoryProvider]
+   C[Packaged Prompt Markdown] --> D[Markdown Prompt Provider]
+   E[Packaged Markdown] --> F[Docs Registry]
+   B --> G[FastMCP]
+   D --> G
+   F --> G
+   G --> H[MCP Transport]
+   H --> K[FastAPI Application]
+   L[Pre-built site] --> M[Static /docs Mount]
+   K --> M
+```
+
+Runtime guarantees:
+
+1. Providers are installed before serving requests.
+2. Prompt discovery rescans authored files on each list and get request.
+3. Duplicate components fail according to FastMCP's configured duplicate policy.
+4. Skills and prompts use native FastMCP component surfaces.
+5. General docs path parsing rejects traversal, backslashes, non-Markdown paths, and the skill namespace.
+
+## Build And Publish Flow
+
+1. Author prompt definitions and prose under `docs/prompts/`.
+2. Run `uv run zensical build` to produce `site/`.
+3. Build the wheel, which packages the authored docs under `personal_mcp/docs/`.
+4. Start the app and serve MCP plus the static site.
+
+No runtime Markdown-to-HTML conversion occurs.
+
+## Machine-Facing Mapping
+
+1. `docs/skills/<skill-id>/SKILL.md` maps to `skill://<skill-id>/SKILL.md`.
+2. Skill supporting files map to `skill://<skill-id>/<path>`.
+3. Declarative prompt documents map to native MCP prompt names.
+4. General `docs/<path>.md` maps to `resource://docs/{path*}`.
+
+The server publishes no tool projections of resources or prompts.
+
+## Public Surface Policy
+
+Canonical provider and protocol surfaces are the only public interfaces.
+
+## Static Mount Expectations
+
+The FastAPI app mounts the Zensical output, serves index and asset files, and returns a clear unavailable response when the static output is absent. The site directory is immutable for a given build and remains separate from packaged authored Markdown.

src/personal_mcp/docs/prompts/authoring/PROMPT.md

@@ -1,33 +1,21 @@
 ---
-name: authoring
+icon: lucide/messages-square
+prompt:
+  version: "1.0.0"
   description: Provide a practical checklist and baseline template for authoring docs-first MCP modules and repository-specific Copilot instruction shims.
-x-personal-mcp:
-  id: authoring
-  version: 1.0.0
-  tags:
-    - authoring
-    - mcp
-    - fastmcp
-    - copilot
-    - prompts
-    - scaffolding
-  capabilities:
-    - resource://prompts/authoring/document
+  tags: [authoring, mcp, fastmcp, copilot, prompts, scaffolding]
   arguments:
     artifact_type:
-      title: Artifact type
-      description: "Enum (case-sensitive): skill | prompt | shim."
+      description: Artifact type to create.
       required: true
+      choices: [skill, prompt, shim]
     artifact_id:
-      title: Artifact id
       description: Lowercase kebab-case id for the module or shim.
       required: true
     goal:
-      title: Goal
-      description: One-sentence capability statement describing what to create and when to use it.
+      description: One-sentence capability statement.
       required: true
     scope_glob:
-      title: Scope glob
       description: Optional applyTo glob for shim outputs.
       required: false
 ---
@@ -36,6 +24,13 @@ x-personal-mcp:
 
 Use this prompt to author or update docs-first MCP modules in this repository, including repository-specific Copilot thin shims.
 
+## Supplied Inputs
+
+- `artifact_type`: {{artifact_type}}
+- `artifact_id`: {{artifact_id}}
+- `goal`: {{goal}}
+- `scope_glob`: {{scope_glob}}
+
 ## Inputs
 
 1. artifact_type: one of skill, prompt, shim
@@ -51,7 +46,7 @@ Load only what matches the requested artifact:
 2. Prompt metadata and structure: [Prompt Contract](../../contracts/prompt.md)
 3. Skill metadata and structure (only for skill outputs): [Skill Contract](../../contracts/skill_contract.md)
 4. Thin shim mechanics and path binding: [Skill Usage Mechanics](../../usage.md)
-5. Copilot resource attachment and fallback behavior: [Copilot MCP Mechanics](../../copilot.md)
+5. Copilot resource attachment behavior: [Copilot MCP Mechanics](../../copilot.md)
 
 ## Workflow
 
@@ -70,11 +65,8 @@ Load only what matches the requested artifact:
 8. Keep guidance deterministic and minimal, with explicit references to source docs.
 9. If artifact_type is shim:
   - bind one applyTo scope to one `skill://<name>/SKILL.md` resource URI
-   - prefer MCP resource attachment first
+  - use MCP resource attachment
   - inspect the selected skill's `_manifest` only when supporting material is needed
-  - if resource attachment is unavailable, use the generic fallback tools:
-     1. list_resources
-     2. read_resource
 10. Return created or updated file paths and any validation commands that should be run.
 
 ## Output Contract

src/personal_mcp/docs/prompts/greenfield-architecture/PROMPT.md

@@ -1,33 +1,21 @@
 ---
-name: greenfield-architecture
+icon: lucide/messages-square
+prompt:
+   version: "1.0.0"
    description: Research established patterns and design a high-level architecture for a new app or library with explicit tradeoffs and test strategy.
-x-personal-mcp:
-  id: greenfield-architecture
-  version: 1.0.0
-  tags:
-    - architecture
-    - planning
-    - greenfield
-    - design
-    - testing
-    - prompts
-  capabilities:
-    - resource://prompts/greenfield-architecture/document
+   tags: [architecture, planning, greenfield, design, testing, prompts]
    arguments:
       scope_type:
-      title: Scope type
-      description: "Scope type: app or library."
+         description: Scope type to design.
          required: true
+         choices: [app, library]
       intent_document:
-      title: Intent document
-      description: Optional full document describing goals, context, and desired outcomes.
+         description: Optional full document describing goals and context.
          required: false
       problem_domain:
-      title: Problem domain
-      description: Domain and business goal for the new app or library when no full intent document is provided.
+         description: Problem domain and business goal.
          required: false
       constraints:
-      title: Constraints
          description: Runtime, deployment, and non-functional constraints.
          required: false
 ---
@@ -36,6 +24,13 @@ x-personal-mcp:
 
 Use this prompt to design a new software app or library architecture in generic terms.
 
+## Supplied Inputs
+
+- `scope_type`: {{scope_type}}
+- `intent_document`: {{intent_document}}
+- `problem_domain`: {{problem_domain}}
+- `constraints`: {{constraints}}
+
 ## Inputs
 
 1. intent_document: optional full document that explains goals, context, constraints, and desired outcomes

src/personal_mcp/docs/prompts/jsfiddle-page-layout/PROMPT.md

@@ -1,25 +1,27 @@
 ---
-name: jsfiddle-page-layout
+icon: lucide/messages-square
+prompt:
+  version: "1.1.0"
   description: Create a responsive sample page layout for a user-supplied domain and return paste-ready HTML and CSS for JSFiddle.
-x-personal-mcp:
-  id: jsfiddle-page-layout
-  version: 1.1.0
-  tags:
-    - frontend
-    - html
-    - css
-    - jsfiddle
-    - layout
-    - prototyping
-    - prompts
-  capabilities:
-    - resource://prompts/jsfiddle-page-layout/document
+  tags: [frontend, html, css, jsfiddle, layout, prototyping, prompts]
+  arguments:
+    domain:
+      description: Product, service, organization, or subject represented by the page.
+      required: true
+    layout_brief:
+      description: Optional page type, sections, priorities, or visual constraints.
+      required: false
 ---
 
 # JSFiddle Page Layout
 
 Create a polished sample page layout for the supplied domain. The result must run by pasting the markup and styles into the [JSFiddle](https://jsfiddle.net/) HTML and CSS panes.
 
+## Supplied Inputs
+
+- `domain`: {{domain}}
+- `layout_brief`: {{layout_brief}}
+
 ## Inputs
 
 1. `domain`: the product, service, organization, or subject represented by the page, including its intended audience when known

src/personal_mcp/docs/prompts/mcp-consumer-repo-shim/PROMPT.md

@@ -1,29 +1,21 @@
 ---
-name: mcp-consumer-repo-shim
-description: Create one repository-specific thin shim instruction file that binds a file scope to a user-selected Personal MCP skill resource and enforces resource-first Copilot retrieval behavior.
-x-personal-mcp:
-  id: mcp-consumer-repo-shim
-  version: 1.0.0
-  tags:
-    - copilot
-    - mcp
-    - instructions
-    - shims
-    - prompts
-  capabilities:
-    - resource://prompts/mcp-consumer-repo-shim/document
+icon: lucide/messages-square
+prompt:
+  version: "1.0.0"
+  description: Create one repository-specific thin shim instruction file that binds a file scope to a user-selected Personal MCP skill resource.
+  tags: [copilot, mcp, instructions, shims, prompts]
   arguments:
     apply_to_glob:
-      description: File glob scope for the shim applyTo field, such as tests/** or **/*.md.
+      description: File glob scope for the shim applyTo field.
       required: true
     primary_skill_resource:
-      description: Primary native skill resource URI in the form skill://<skill-name>/SKILL.md.
+      description: Primary native skill:// resource URI.
       required: true
     shim_title:
-      description: Human-readable name for the instruction shim frontmatter.
+      description: Optional human-readable instruction shim name.
       required: false
     companion_docs_page:
-      description: Optional relative docs link for human-facing companion guidance.
+      description: Optional relative companion documentation link.
       required: false
 ---
 
@@ -31,6 +23,13 @@ x-personal-mcp:
 
 Use this prompt to generate exactly one repository-scoped Copilot instruction shim for an MCP consumer repository.
 
+## Supplied Inputs
+
+- `apply_to_glob`: {{apply_to_glob}}
+- `primary_skill_resource`: {{primary_skill_resource}}
+- `shim_title`: {{shim_title}}
+- `companion_docs_page`: {{companion_docs_page}}
+
 ## Inputs
 
 - Required:
@@ -45,7 +44,7 @@ Use this prompt to generate exactly one repository-scoped Copilot instruction sh
 Load only sections relevant to the requested shim:
 
 1. Thin shim pattern and scope guidance: [Skill Usage Mechanics](../../usage.md)
-2. VS Code Copilot MCP behavior and fallback mechanics: [Copilot MCP Mechanics](../../copilot.md)
+2. VS Code Copilot MCP resource behavior: [Copilot MCP Mechanics](../../copilot.md)
 3. Authoring workflow and validation checklist: [Authoring Guide](../../authoring.md)
 4. Instruction metadata expectations and examples: [Copilot customization skill](../../skills/copilot-customization/SKILL.md)
 
@@ -60,11 +59,8 @@ Load only sections relevant to the requested shim:
    - include a primary rule that uses the selected primary_skill_resource first
    - include a bounded execution pattern (load primary doc, apply only relevant sections, keep edits minimal)
 6. Include VS Code/Copilot integration mechanics in the shim body:
-   - prefer MCP resource attachment when available
+  - use MCP resource attachment
   - inspect `_manifest` only when the task needs supporting material
-  - if attachment is unavailable, use the generic fallback tools:
-     1. list_resources
-     2. read_resource
    - ask one clarifying question when confidence is low
 7. If companion_docs_page is provided, include it as a companion docs link line.
 8. Do not generate additional files, code changes, or batch shim packs.
@@ -98,8 +94,7 @@ Execution pattern:
 3. Keep edits minimal and aligned with repository conventions.
 4. Prefer MCP resource attachment when available in the current chat surface.
 5. Read the selected skill's `_manifest` only when supporting material is needed.
-6. If MCP resource attachment is unavailable, use `list_resources` and `read_resource`.
-7. If confidence is low, ask one clarifying question before editing.
+6. If confidence is low, ask one clarifying question before editing.
 
 Companion docs page: <optional-relative-doc-link>
 ```

src/personal_mcp/docs/prompts/nicegui-component-extraction/PROMPT.md

@@ -1,34 +1,21 @@
 ---
-name: nicegui-component-extraction
-description: Extract a user-selected component from a JSFiddle page layout and implement it as a reusable NiceGUI render function with responsive styling and typed bindable state where needed.
-x-personal-mcp:
-  id: nicegui-component-extraction
-  version: 1.0.0
-  tags:
-    - nicegui
-    - components
-    - frontend
-    - refactoring
-    - jsfiddle
-    - prompts
-  capabilities:
-    - resource://prompts/nicegui-component-extraction/document
+icon: lucide/messages-square
+prompt:
+   version: "1.0.0"
+   description: Extract a user-selected component from a JSFiddle page layout and implement it as a reusable NiceGUI render function.
+   tags: [nicegui, components, frontend, refactoring, jsfiddle, prompts]
    arguments:
       component:
-      title: Component
-      description: Component or page region to extract, identified by its visible label, semantic role, or selector.
+         description: Visible label, semantic role, or selector identifying the component.
          required: true
       source_layout:
-      title: Source layout
-      description: Optional HTML and CSS from the JSFiddle page layout prompt; when omitted, use the latest applicable output in the conversation.
+         description: Optional source HTML and CSS.
          required: false
       target_location:
-      title: Target location
-      description: Optional target NiceGUI page, module, or package in which to create and integrate the component.
+         description: Optional target NiceGUI page, module, or package.
          required: false
       behavior_requirements:
-      title: Behavior requirements
-      description: Optional interactions, state, callbacks, or content variations the extracted component must support.
+         description: Optional interactions, state, callbacks, or variations.
          required: false
 ---
 
@@ -36,6 +23,13 @@ x-personal-mcp:
 
 Extract one user-selected component from the output of the [JSFiddle Page Layout](../jsfiddle-page-layout/PROMPT.md) prompt and implement it as a reusable NiceGUI component in the target repository.
 
+## Supplied Inputs
+
+- `component`: {{component}}
+- `source_layout`: {{source_layout}}
+- `target_location`: {{target_location}}
+- `behavior_requirements`: {{behavior_requirements}}
+
 ## Inputs
 
 1. `component`: required visible label, semantic role, or selector identifying the component to extract
@@ -47,10 +41,11 @@ If the selected component or source layout cannot be identified unambiguously, a
 
 ## Required References
 
-Apply both references before implementation:
+Apply these references before implementation:
 
-1. Component boundaries, responsive layout, Quasar props, Tailwind utilities, and shared CSS: [NiceGUI Page Layout and Styling](../../skills/nicegui/references/architecture-and-styling.md)
-2. Typed UI state, propagation, mutable defaults, binding strictness, and version checks: [Binding Dataclasses Deep Dive](../../skills/nicegui/references/binding-dataclasses.md)
+1. Package boundaries, dependency direction, and page or component ownership: [NiceGUI Application Architecture](../../skills/nicegui/references/architecture.md)
+2. Responsive layout, Quasar props, Tailwind utilities, and shared CSS: [NiceGUI Styling and Customization](../../skills/nicegui/references/styling-and-customization.md)
+3. Typed UI state, propagation, mutable defaults, binding strictness, and version checks: [Binding Dataclasses Deep Dive](../../skills/nicegui/references/binding-dataclasses.md)
 
 ## Workflow
 

src/personal_mcp/docs/prompts/pytest-fill-scaffold/PROMPT.md

@@ -1,16 +1,9 @@
 ---
-name: pytest-fill-scaffold
-description: Fill scaffolded pytest test methods with assertions, fixtures, and minimal test data while preserving concise test names and one-line intent docstrings.
-x-personal-mcp:
-  id: pytest-fill-scaffold
-  version: 1.0.0
-  tags:
-    - pytest
-    - testing
-    - scaffolding
-    - prompts
-  capabilities:
-    - resource://prompts/pytest-fill-scaffold/document
+icon: lucide/messages-square
+prompt:
+   version: "1.0.0"
+   description: Fill scaffolded pytest methods with assertions, fixtures, and minimal test data while preserving reviewed structure.
+   tags: [pytest, testing, scaffolding, prompts]
    arguments:
       target_files:
          description: Target test file paths under tests/.
@@ -18,11 +11,12 @@ x-personal-mcp:
       stack:
          description: Runtime stack type for fixture and marker choices.
          required: true
+         choices: [pure-python, fastapi, sqlalchemy-sync, sqlalchemy-async, mixed]
       strategy:
-      description: Balance between minimal and comprehensive implementation.
+         description: Optional minimal or comprehensive implementation preference.
          required: false
       marker_lane:
-      description: Preferred marker lane when applicable.
+         description: Optional pytest marker lane.
          required: false
 ---
 
@@ -30,6 +24,13 @@ x-personal-mcp:
 
 Use this prompt after test scaffolding exists and method names/docstrings are already in place.
 
+## Supplied Inputs
+
+- `target_files`: {{target_files}}
+- `stack`: {{stack}}
+- `strategy`: {{strategy}}
+- `marker_lane`: {{marker_lane}}
+
 ## Inputs
 
 - Target test file(s) under tests/.

src/personal_mcp/docs/prompts/pytest-scaffold/PROMPT.md

@@ -1,28 +1,22 @@
 ---
-name: pytest-scaffold
-description: Plan and optionally scaffold pytest file and class structure for selected Python modules while preserving concise behavior-focused test names and one-line intent docstrings.
-x-personal-mcp:
-  id: pytest-scaffold
-  version: 1.0.0
-  tags:
-    - pytest
-    - testing
-    - scaffolding
-    - prompts
-  capabilities:
-    - resource://prompts/pytest-scaffold/document
+icon: lucide/messages-square
+prompt:
+  version: "1.0.0"
+  description: Plan and optionally scaffold pytest file and class structure for selected Python modules.
+  tags: [pytest, testing, scaffolding, prompts]
   arguments:
     target_modules:
-      description: Target module path(s) under src/.
+      description: Target module paths under src/.
       required: true
     mode:
-      description: Execution mode, either plan-only or scaffold.
+      description: Whether to plan only or create scaffold files.
       required: true
+      choices: [plan-only, scaffold]
     path_strategy:
-      description: Optional mapping preference for src to tests paths.
+      description: Optional src-to-tests path mapping preference.
       required: false
     naming_style:
-      description: Optional preference for concise method naming style.
+      description: Optional concise test naming preference.
       required: false
 ---
 
@@ -30,6 +24,13 @@ x-personal-mcp:
 
 Use this prompt to consistently plan and scaffold pytest test modules for selected Python source modules.
 
+## Supplied Inputs
+
+- `target_modules`: {{target_modules}}
+- `mode`: {{mode}}
+- `path_strategy`: {{path_strategy}}
+- `naming_style`: {{naming_style}}
+
 ## Inputs
 
 - Required:

src/personal_mcp/docs/skills/copilot-customization/SKILL.md

@@ -66,7 +66,6 @@ Choose one of these patterns:
   - Read selected supporting files at `skill://<skill-name>/<supporting-path>`.
 2. Discovery-first strategy:
   - List resources, compare native main-resource names and descriptions, then load the best matching `SKILL.md`.
-  - In tool-only clients, use only `list_resources` and `read_resource` for the same sequence.
 
 ### Authoring guidance for shims
 

src/personal_mcp/docs/skills/nicegui/SKILL.md

@@ -48,13 +48,13 @@ Load [FastAPI and Uvicorn startup](./references/fastapi-uvicorn-startup.md) for:
 - exposing programmatic startup through `[project.scripts]`
 - reload, worker, and process-local state constraints
 
-### Components And Styling
+### Styling And Customization
 
-Load [architecture and styling](./references/architecture-and-styling.md) for:
+Load [styling and customization](./references/styling-and-customization.md) for:
 
-- page, component, and service boundaries
-- component extraction decisions
-- Quasar props, Tailwind utilities, and custom CSS boundaries
+- progressive discovery through NiceGUI docs, constructors, and Quasar docs
+- Quasar props, slots, events, and NiceGUI customization methods
+- Tailwind for structural styling and static stylesheets for fine tuning
 - responsive layout and static asset conventions
 - Tailwind and Quasar breakpoint scales, container queries, and responsive testing
 - uniformly scaling dialogs on mobile
@@ -63,6 +63,15 @@ Load [architecture and styling](./references/architecture-and-styling.md) for:
 - sizing scrollable dialog cards under CSS `zoom`
 - validating zoomed controls with Playwright or a browser
 
+### Special Component Customization
+
+Load [special component customization](./references/special-component-customization.md) for:
+
+- the required source-research gate before generating component customizations
+- `ui.select` constructors, Quasar props, slots, detached popups, and option caveats
+- `ui.icon` names, icon families, sizing, colors, assets, and Material Symbol variants
+- component-specific accessibility, sanitization, and validation checks
+
 ### Bindable State
 
 Load [bindable dataclasses](./references/binding-dataclasses.md) for:
@@ -103,12 +112,14 @@ Load [source documentation](./references/source-documentation.md) when:
 
 1. Load [application architecture](./references/architecture.md).
 2. Add [FastAPI and Uvicorn startup](./references/fastapi-uvicorn-startup.md) when FastAPI owns the application or startup must be exposed as a project command.
-3. Add [architecture and styling](./references/architecture-and-styling.md) only when page and component design is in scope.
+3. Add [styling and customization](./references/styling-and-customization.md) only when page layout or visual customization is in scope.
 
 ### Page Or Component Work
 
-1. Load [architecture and styling](./references/architecture-and-styling.md).
-2. Add [interaction patterns](./references/interaction-patterns.md) or [bindable dataclasses](./references/binding-dataclasses.md) according to the page behavior.
+1. Load [application architecture](./references/architecture.md) for page and component ownership decisions.
+2. Load [styling and customization](./references/styling-and-customization.md) for layout, responsive behavior, or visual customization.
+3. Add [special component customization](./references/special-component-customization.md) when the work targets `ui.select`, `ui.icon`, or another component with specialized Quasar behavior.
+4. Add [interaction patterns](./references/interaction-patterns.md) or [bindable dataclasses](./references/binding-dataclasses.md) according to the page behavior.
 
 ### Debugging Or Production Review
 
@@ -122,7 +133,9 @@ Load [source documentation](./references/source-documentation.md) when:
 - Keep business logic out of UI components and event handlers.
 - Avoid blocking I/O and CPU-heavy work in the UI event loop.
 - Prefer event-driven updates and explicit refreshes over unrelated polling.
-- Prefer Tailwind utilities, then Quasar props, then reusable component helpers; use minimal shared CSS when those are insufficient.
+- Discover component capabilities through NiceGUI docs and constructors, then the wrapped Quasar API.
+- Research the current NiceGUI and Quasar source documentation before generating component-specific code or CSS.
+- Prefer constructor arguments and native Quasar features through NiceGUI; use Tailwind for structure and scoped static CSS for stable fine tuning.
 - Provide loading, success, and failure states for user-triggered work.
 - Treat version-specific guidance as a prompt to verify the project's dependency version.
 

src/personal_mcp/docs/skills/nicegui/references/architecture.md

@@ -23,7 +23,6 @@ Recommended base shape:
 │  └─ app/
 │     ├─ __init__.py
 │     ├─ main.py
-│     ├─ bootstrap.py
 │     ├─ config.py
 │     ├─ logging.py
 │     ├─ api/
@@ -69,6 +68,14 @@ Prefer:
 
 Avoid imports from services back into API or UI modules.
 
+## Page And Component Ownership
+
+Page modules compose routes from presentation components and service calls. They should not own domain rules, persistence, or long-running synchronous work.
+
+Extract a presentation pattern to `ui/components/` when it appears on two or more pages or owns a meaningful interaction boundary. Keep one-off route composition in the page module. Reusable components should accept data and event callbacks instead of importing page state or business services implicitly.
+
+For page composition, responsive layout, Quasar props, and CSS customization, load [styling and customization](./styling-and-customization.md).
+
 ## Optional Persistence
 
 Use only when the product requires durable data.

src/personal_mcp/docs/skills/nicegui/references/source-documentation.md

@@ -5,6 +5,9 @@ Use these links to verify framework-specific behavior before relying on version-
 ## NiceGUI
 
 !!! info "NiceGUI sources"
+    - [Component documentation](https://nicegui.io/documentation)
+    - [Element styling, props, and events](https://nicegui.io/documentation/element)
+    - [NiceGUI element source](https://github.com/zauberzeug/nicegui/tree/main/nicegui/elements)
     - [Pages, routing, and FastAPI integration](https://www.nicegui.io/documentation/section_pages_routing)
     - [`ui.run_with` implementation](https://github.com/zauberzeug/nicegui/blob/main/nicegui/ui_run_with.py)
     - [FastAPI integration example](https://github.com/zauberzeug/nicegui/blob/main/examples/fastapi/main.py)

src/personal_mcp/docs/skills/nicegui/references/special-component-customization.md

@@ -0,0 +1,144 @@
+# NiceGUI Special Component Customization
+
+Use this reference for components whose NiceGUI wrapper, Quasar implementation, popup behavior, slots, or external assets require component-specific handling. Start with [styling and customization](./styling-and-customization.md) for the general escalation workflow.
+
+## Source Research Gate
+
+Research the target component before generating code or CSS. Do not rely on a remembered NiceGUI or Quasar API.
+
+For each component:
+
+1. Read its current NiceGUI documentation page.
+2. Inspect the constructor and implementation in the target project's installed NiceGUI package.
+3. Confirm the wrapped Quasar component in the NiceGUI source.
+4. Read the matching Quasar guide and API definition for props, slots, events, and methods.
+5. Check the target project's pinned NiceGUI version before using current upstream behavior.
+6. Record which layer owns each proposed customization before writing it.
+
+Use current upstream source only as a fallback when the target environment is unavailable. If installed and upstream behavior differ, follow the installed version and state the difference.
+
+## `ui.select`
+
+### Source Map
+
+- [NiceGUI `ui.select` documentation](https://nicegui.io/documentation/select)
+- [NiceGUI `Select` source](https://github.com/zauberzeug/nicegui/blob/main/nicegui/elements/select.py)
+- [Quasar `QSelect` guide](https://quasar.dev/vue-components/select/)
+- [Quasar `QSelect` API source](https://github.com/quasarframework/quasar/blob/dev/ui/src/components/select/QSelect.json)
+
+NiceGUI's `Select` wraps Quasar `QSelect` but owns important Python-side behavior. Its constructor handles options, labels, values, change callbacks, input filtering, new-value modes, multiple selection, clearing, validation, and key generation. Use those constructor parameters before adding equivalent Quasar props manually.
+
+### Customization Order
+
+1. Use `options`, `label`, `value`, `on_change`, `with_input`, `new_value_mode`, `multiple`, `clearable`, `validation`, and `key_generator` through the NiceGUI constructor.
+2. Use `.props()` for additional documented `QSelect` behavior such as field design, chips, option density, popup classes, popup positioning, or menu/dialog behavior.
+3. Use `.classes()` and Tailwind for the field's structural width and placement.
+4. Use named slots for prepend, append, loading, no-option, selected, or option content when props are insufficient.
+5. Use `popup-content-class` to attach an application class to the detached options popup, then fine-tune it in a static stylesheet.
+
+```python
+from nicegui import ui
+
+item_select = ui.select(
+    options={"chair": "Chair", "desk": "Desk", "lamp": "Lamp"},
+    label="Items",
+    multiple=True,
+    clearable=True,
+    with_input=True,
+).props(
+    "outlined use-chips options-dense "
+    "popup-content-class=app-item-select-menu"
+).classes(
+    "w-full md:max-w-md"
+)
+
+with item_select.add_slot("prepend"):
+    ui.icon("inventory_2")
+```
+
+```css
+.app-item-select-menu {
+    max-height: min(24rem, 60dvh);
+}
+```
+
+### Select-Specific Caveats
+
+- NiceGUI accepts a list of values or a dictionary mapping values to labels. Do not assume the Python options model is the same as Quasar's JavaScript object-array examples.
+- After mutating `options`, call `update()` or use `set_options()` so the client receives the change.
+- `new_value_mode` enables input automatically. For dictionary options with `add`, NiceGUI requires a `key_generator`.
+- A multiple select has a list value. NiceGUI normalizes a non-list initial value, but application state should still use the intended list shape.
+- `map-options` has a Quasar performance cost. Do not add it to NiceGUI's mapped options without confirming that the wrapper's value translation requires it.
+- `display-value-html` and `options-html` can create cross-site scripting risk. When using `selected`, `selected-item`, or `option` slots, the application owns sanitization.
+- Custom option slots use virtual scrolling. When one option renders multiple sibling elements, Quasar requires `q-virtual-scroll--with-prev` on every additional sibling.
+- Buttons placed in `before`, `after`, `prepend`, or `append` field slots do not propagate clicks to the parent. A submit button in one of those slots needs its own submit handler.
+- `QSelect` renders its popup outside the field. Style it through `popup-content-class`; do not assume a descendant selector beneath the field will reach it.
+- Quasar switches between menu and dialog popup behavior by platform. Verify forced `behavior=menu` carefully on iOS when input filtering is enabled.
+
+Use `.on()` or `run_method()` only after confirming the event or method in the installed Quasar API. Prefer NiceGUI's `on_change`, `set_options()`, value bindings, and `is_showing_popup` when they cover the behavior.
+
+## `ui.icon`
+
+### Source Map
+
+- [NiceGUI `ui.icon` documentation](https://nicegui.io/documentation/icon)
+- [NiceGUI `Icon` source](https://github.com/zauberzeug/nicegui/blob/main/nicegui/elements/icon.py)
+- [Quasar `QIcon` guide](https://quasar.dev/vue-components/icon/)
+- [Quasar `QIcon` API source](https://github.com/quasarframework/quasar/blob/dev/ui/src/components/icon/QIcon.json)
+- [Google Material Symbols and Icons](https://fonts.google.com/icons)
+
+NiceGUI's `Icon` is a thin `QIcon` wrapper. Its constructor exposes `name`, `size`, and `color`; the source forwards these to a `q-icon` element. Use Quasar's icon naming and asset rules for anything beyond those parameters.
+
+### Customization Order
+
+1. Choose an icon family that is actually loaded by the application.
+2. Pass the documented icon name, size, and color to `ui.icon()`.
+3. Use `.props()` for supported `QIcon` props such as `left`, `right`, or a custom render tag.
+4. Use `.classes()` for structural placement and an application class for stable visual variants.
+5. Use a static stylesheet for Material Symbol axes, state variants, custom webfonts, or repeated effects.
+
+```python
+from nicegui import ui
+
+ui.icon(
+    "sym_o_home",
+    size="1.5rem",
+    color="primary",
+).classes(
+    "app-symbol-filled shrink-0"
+).tooltip(
+    "Home"
+)
+```
+
+```css
+.app-symbol-filled {
+    font-variation-settings:
+        "FILL" 1,
+        "wght" 400,
+        "GRAD" 0,
+        "opsz" 24;
+}
+```
+
+### Icon-Specific Caveats
+
+- Material icon names use snake case. Material variants use prefixes such as `o_`, `r_`, `s_`, `sym_o_`, `sym_r_`, and `sym_s_`.
+- Other icon families have their own prefixes and require their webfont or stylesheet to be loaded. A valid name does not load the corresponding asset.
+- `size` accepts CSS units or Quasar sizes such as `xs`, `sm`, `md`, `lg`, and `xl`. Quasar implements icon sizing through `font-size`.
+- Icon color inherits text color unless the `color` prop or a CSS color overrides it.
+- Material Symbol variable axes apply to webfont icons, not static SVG icon exports.
+- Quasar also supports SVG path strings, `svguse:` references, and `img:` URLs. Confirm the exact `QIcon` name format and mount path before generating one of these forms.
+- For an action, use a semantic control such as `ui.button(icon=..., on_click=...)` and give it an accessible label or tooltip. Do not turn a bare decorative icon into an unlabeled control.
+- Prefer `ui.icon(...).tooltip(...)` over manually constructing tooltip slot markup when NiceGUI's method covers the requirement.
+
+## Completion Check
+
+Before accepting a special-component customization:
+
+1. Cite the NiceGUI component page and implementation that were inspected.
+2. Cite the matching Quasar guide or API source.
+3. Identify constructor arguments, Quasar props, slots, Tailwind classes, and stylesheet rules separately.
+4. Confirm detached popup or external asset behavior where applicable.
+5. Test keyboard interaction, focus, labels, and tooltips.
+6. Test the supported mobile, landscape desktop, and portrait desktop viewports.

src/personal_mcp/docs/skills/nicegui/references/styling-and-customization.md

@@ -0,0 +1,334 @@
+# NiceGUI Styling And Customization
+
+Use this reference to discover how a NiceGUI component can be customized, apply the least invasive supported mechanism, and introduce CSS without fighting Quasar's internal geometry.
+
+For package boundaries, dependency direction, and page or component ownership, load [application architecture](./architecture.md).
+
+## Progressive Customization Workflow
+
+Increase the customization level only when the previous source does not expose what the design requires:
+
+1. Read the NiceGUI documentation page for the component.
+2. Inspect the NiceGUI element function or class constructor.
+3. Identify the wrapped Quasar component and read its documentation.
+4. Use Quasar props, slots, and events through NiceGUI's native customization APIs.
+5. Use Tailwind classes for structural layout.
+6. Add a scoped static stylesheet for stable visual fine tuning.
+
+Stop as soon as the required behavior is supported. Do not begin by targeting Quasar's generated DOM or internal selectors.
+
+### 1. Start With The NiceGUI Component Page
+
+Find the component in the [NiceGUI documentation](https://nicegui.io/documentation). Check its examples, parameters, methods, events, bindings, and inheritance before writing CSS. The component page establishes the public NiceGUI API and often demonstrates the intended Quasar integration.
+
+Confirm the target project's installed NiceGUI version because the current online documentation can differ from the pinned release.
+
+### 2. Inspect The NiceGUI Constructor
+
+Read the signature and implementation of the imported NiceGUI function or element class. The constructor reveals accepted Python parameters, defaults, event callbacks, validation, and values NiceGUI forwards to the frontend.
+
+Use editor navigation or runtime inspection against the project's selected environment:
+
+```python
+from inspect import getsource, signature
+
+from nicegui import ui
+
+print(signature(ui.select))
+print(getsource(ui.select))
+```
+
+When `ui.<name>` is a factory or alias, follow it to the element class in the [NiceGUI element sources](https://github.com/zauberzeug/nicegui/tree/main/nicegui/elements). Prefer the installed package source when behavior may differ by version.
+
+### 3. Read The Underlying Quasar Component Docs
+
+NiceGUI wraps Quasar components such as [`QInput`](https://quasar.dev/vue-components/input/), [`QSelect`](https://quasar.dev/vue-components/select/), and [`QDialog`](https://quasar.dev/vue-components/dialog/). Use the matching Quasar component page to discover its complete props, slots, events, methods, and behavior notes.
+
+Map Quasar's Vue API onto the NiceGUI wrapper instead of copying a Vue template. Verify that a prop or slot exists in the Quasar version used by the installed NiceGUI release.
+
+### 4. Apply Native Quasar Features Through NiceGUI
+
+Use the NiceGUI element customization methods to reach the supported Quasar surface:
+
+- `.props(...)` for Quasar properties and boolean flags
+- `.classes(...)` for Tailwind utilities and stable application class names
+- `.style(...)` for dynamic inline values or a quick, local probe
+- `.on(...)` for events that are not represented by a constructor callback
+- slots or child elements for Quasar extension points exposed by the wrapper
+
+```python
+with ui.select(
+    options=items,
+    label="Item",
+).props(
+    "outlined clearable options-dense popup-content-class=app-item-menu"
+).classes(
+    "w-full md:max-w-md"
+) as item_select:
+    with item_select.add_slot("prepend"):
+        ui.icon("inventory_2")
+```
+
+Prefer constructor arguments when NiceGUI exposes the behavior directly. Use `.props()` for supported Quasar features that are not constructor parameters. Use slots when the Quasar docs define a semantic insertion point; do not reproduce that content with absolute positioning.
+
+## Structural Styling With Tailwind
+
+Use standard [Tailwind utility classes](https://tailwindcss.com/docs/utility-first) for page and component structure:
+
+- display, flex, and grid behavior
+- width, height, and maximum-width constraints
+- spacing, gaps, padding, and alignment
+- wrapping, overflow, and responsive variants
+- typography and common visual utilities when they fully express the design
+
+Build the outer layout before fine-tuning individual controls:
+
+1. Define the page shell and width constraints.
+2. Establish responsive rows, columns, gaps, and wrapping.
+3. Add semantic sections and repeated visual patterns.
+4. Configure component appearance and behavior with constructor arguments and Quasar props.
+5. Add stable application classes for any remaining stylesheet rules.
+
+```python
+with ui.column().classes("w-full max-w-6xl mx-auto gap-6 px-4"):
+    page_header(title="Inventory")
+
+    with ui.row().classes("w-full gap-4 flex-wrap lg:flex-nowrap items-start"):
+        filters_panel().classes("w-full lg:w-72 shrink-0")
+        item_grid().classes("w-full flex-1 min-w-0")
+```
+
+Use stable width, minimum-width, and flex constraints so labels, icons, validation messages, and loaded content do not shift the surrounding layout.
+
+## Fine Tuning With Static Stylesheets
+
+Move stable fine tuning into a static stylesheet after the structure and native component configuration are correct. Static stylesheets provide reusable selectors, media queries, pseudo-classes, CSS variables, and a clear cascade that inline declarations cannot provide.
+
+Attach an application-owned class with `.classes()` or a Quasar popup prop, then scope stylesheet rules beneath it:
+
+```python
+ui.select(...).props("popup-content-class=app-item-menu").classes(
+    "app-item-select w-full md:max-w-md"
+)
+```
+
+```css
+.app-item-select {
+    --app-field-accent: #176b5b;
+}
+
+.app-item-select:focus-within {
+    filter: drop-shadow(0 0 0.25rem rgb(23 107 91 / 20%));
+}
+
+.app-item-menu {
+    max-height: min(24rem, 60dvh);
+}
+```
+
+Use `.style()` when a value is calculated at runtime or while testing a local hypothesis. Once a declaration becomes stable or repeated, move it to the stylesheet and keep only the application class in Python.
+
+Avoid overriding Quasar internals such as `.q-field__label`, `.q-field__native`, `.q-field__control`, and `.q-field__input` unless the public props, slots, and application-level selectors cannot express the requirement.
+
+Quasar coordinates field height, padding, labels, values, icons, and floating-label transforms. Changing only one internal part tends to cause clipping or overlap.
+
+## Responsive Layout
+
+Support these layouts only:
+
+- mobile: a single-column layout with wrapping toolbars and full-width controls
+- landscape desktop: $1920 \times 1080$ with side-by-side panels where they improve scanning
+- portrait desktop: $1080 \times 1920$ with stacked panels or a narrow fixed sidebar
+
+Build the mobile layout first, then add one desktop breakpoint when a row or grid needs more space. Prefer flex wrapping and fluid grids before adding another breakpoint. Use Tailwind classes for page layout and Quasar props for component behavior.
+
+```python
+with ui.row().classes("w-full flex-wrap gap-4 lg:flex-nowrap items-start"):
+    filters_panel().classes("w-full lg:w-72 shrink-0")
+    item_grid().classes("w-full flex-1 min-w-0")
+```
+
+Use `min-w-0` for flexible children, `flex-wrap` for toolbars, and `max-w-* mx-auto` to keep portrait layouts readable. Do not add device-specific component trees, container queries, or custom breakpoints unless a supported layout demonstrates a concrete failure.
+
+## Loading Stylesheets And Static Assets
+
+- Mount and link static stylesheets once from the composition layer rather than injecting CSS from individual pages.
+- Keep custom CSS tokenized with variables and scoped to application classes.
+- Avoid broad rules against Quasar internals.
+- Mount referenced assets in the composition layer.
+- Verify mount paths, reverse-proxy rewrites, and cache behavior.
+
+```python
+from pathlib import Path
+
+from fastapi.staticfiles import StaticFiles
+
+STATIC_DIR = Path(__file__).parent / "ui" / "static"
+
+app.mount("/static", StaticFiles(directory=STATIC_DIR), name="static")
+ui.add_head_html(
+    '<link rel="stylesheet" href="/static/css/base.css">',
+    shared=True,
+)
+```
+
+## Worked Example: Responsive Dialog Customization
+
+This example begins with normal field density and Quasar popup props, then uses an application class and static stylesheet for the remaining responsive fine tuning. Use whole-card scaling when a form dialog must become uniformly larger on mobile while preserving Quasar's internal proportions. Keep detached select menus unscaled and make the card itself scrollable.
+
+### Use Normal Field Density
+
+Normal Quasar fields are approximately `56px` high, while dense fields are approximately `40px` high. Remove `dense` when larger controls are needed.
+
+```python
+ui.input("Name").props("outlined")
+ui.number("Quantity").props("outlined")
+ui.select(...).props("outlined popup-content-class=app-item-detail-menu")
+ui.textarea("Description").props("outlined autogrow")
+```
+
+Add a scoped class to the dialog card:
+
+```python
+ui.card().classes("app-detail-card app-item-detail-card")
+```
+
+### Scale The Complete Card
+
+```css
+:root {
+    --item-dialog-scale: 1;
+    --item-dialog-max-height: calc(100dvh - 3rem);
+}
+
+.app-item-detail-card {
+    width: min(50rem, 50vw);
+    max-height: var(--item-dialog-max-height);
+    overflow-y: auto;
+    overscroll-behavior: contain;
+    zoom: var(--item-dialog-scale);
+}
+
+/* Restore Quasar's baseline if a global rule overrides it. */
+.app-item-detail-card .q-field,
+.app-item-detail-menu {
+    font-size: 14px;
+}
+
+@media (max-width: 599px) {
+    :root {
+        --item-dialog-scale: 1.2;
+        /* 75dvh becomes 90dvh after 1.2x zoom. */
+        --item-dialog-max-height: 75dvh;
+    }
+
+    .app-item-detail-card {
+        width: 80vw;
+    }
+
+    .app-item-detail-menu {
+        font-size: 16.8px;
+    }
+}
+```
+
+The main mobile tuning knob is:
+
+```css
+--item-dialog-scale: 1.2;
+```
+
+### Keep Detached Popups Unscaled
+
+Do not apply `zoom` or `transform: scale()` to a `QSelect` popup menu. Quasar renders menus outside the dialog and positions them from the unscaled anchor geometry. Scaling the menu container afterward separates it from its field.
+
+Avoid:
+
+```css
+.app-item-detail-card,
+.app-item-detail-menu {
+    zoom: 1.2;
+}
+```
+
+Use:
+
+```css
+.app-item-detail-card {
+    zoom: 1.2;
+}
+
+.app-item-detail-menu {
+    font-size: 16.8px;
+}
+```
+
+Use `popup-content-class=app-item-detail-menu` to target the detached menu and enlarge its text without changing its coordinate system.
+
+### Account For Zoom When Scrolling
+
+The card's pre-zoom maximum height must account for the scale:
+
+\[
+\begin{aligned}
+h_{\mathrm{pre}} &= \frac{h_{\mathrm{visible}}}{s} \\
+\text{where } s &= \text{the zoom scale}
+\end{aligned}
+\]
+
+For a desired visual height of `90dvh` at \(1.2\times\):
+
+\[
+\frac{90\,\mathrm{dvh}}{1.2} = 75\,\mathrm{dvh}
+\]
+
+Therefore:
+
+```css
+--item-dialog-max-height: 75dvh;
+```
+
+Apply scrolling to the card itself:
+
+```css
+.app-item-detail-card {
+    max-height: var(--item-dialog-max-height);
+    overflow-y: auto;
+    overscroll-behavior: contain;
+}
+```
+
+This keeps the dimmed page stationary while the form scrolls.
+
+### Match The Quasar Breakpoint
+
+Quasar's extra-small breakpoint ends at `599.98px`. A mobile-only rule can use:
+
+```css
+@media (max-width: 599px) {
+    /* Mobile rules. */
+}
+```
+
+Confirm custom breakpoint values against the target application's Quasar configuration.
+
+## Validation Checklist
+
+Check each completed page at these three viewports:
+
+1. A representative mobile viewport, such as $390 \times 844$.
+2. Landscape desktop at $1920 \times 1080$.
+3. Portrait desktop at $1080 \times 1920$.
+
+Confirm that page sections do not overlap, toolbars wrap on mobile, desktop panels use the available space without becoming excessively wide, and dialogs remain visible and scroll to their final field.
+
+## Sources
+
+!!! info "Primary sources"
+    - [NiceGUI element styling and props](https://nicegui.io/documentation/element)
+    - [NiceGUI binding properties](https://nicegui.io/documentation/section_binding_properties)
+    - [Quasar components](https://quasar.dev/vue-components)
+    - [Quasar field](https://quasar.dev/vue-components/field/)
+    - [Quasar select](https://quasar.dev/vue-components/select/)
+    - [Tailwind responsive design](https://tailwindcss.com/docs/responsive-design)
+    - [MDN `zoom`](https://developer.mozilla.org/en-US/docs/Web/CSS/zoom)