@laitszkin/apollo-toolkit 3.11.7 → 3.12.0

package/archive-specs/references/templates/principles.md

@@ -1,28 +0,0 @@
-# <慣例類別>
-
-[One-sentence summary of what this convention area covers.]
-
-## <慣例名稱>
-
-<慣例描述>
-
-**理由**: <為什麼採用此慣例>
-
-**範例**: <從代碼庫提取的具體範例>
-
-## <慣例名稱>
-
-<慣例描述>
-
-**理由**: <為什麼採用此慣例>
-
-**範例**: <從代碼庫提取的具體範例>
-
----
-
-## Writing Rules
-
-- Each file covers one convention area (e.g., naming, coding style, dependency management, error handling, testing).
-- State the convention clearly.
-- Provide rationale traceable to the codebase.
-- Include a brief example from the codebase, not an invented one.

package/maintain-skill-catalog/README.md

@@ -1,18 +0,0 @@
-# maintain-skill-catalog
-
-Maintain a repository of installable skills by auditing skill definitions, dependency declarations, shared conventions, and catalog validation.
-
-## Core capabilities
-
-- Scans top-level skills before adding or splitting new ones to avoid duplicate scope.
-- Audits standardized `## Dependencies` sections and separates vendored, local-only, external, and alias dependencies.
-- Syncs catalog docs such as `README.md` and `AGENTS.md/CLAUDE.md` with actual skill capabilities.
-- Catches catalog-wide validation issues like missing `agents/openai.yaml` files or stale prompt references.
-- Encodes user corrections into durable catalog rules so the same classification mistakes do not repeat.
-
-## Typical triggers
-
-- Standardize all skills to one dependency format.
-- Check which skills rely on external skills and document how to install them.
-- Split repeated workflow steps into a new shared skill.
-- Fix skill-catalog CI failures caused by missing metadata or agent config files.

package/maintain-skill-catalog/SKILL.md

@@ -1,72 +0,0 @@
----
-name: maintain-skill-catalog
-description: >-
-  Maintain this SKILL catalog repo: reconcile `SKILL.md` frontmatter/`Dependencies`, `agents/openai.yaml`, README inventory, classify vendored vs external vs unpublished-local aliases, prefer extracting shared workflows over duplicating long prose, and always rerun `apltk validate-skill-frontmatter` plus `apltk validate-openai-agent-config` before finishing—never invent package names or installers for unverified deps.
-  Use when CI metadata breaks, users ask to “sync skills”, or dependency docs drift. Do not use for random application repos that are not this catalog layout.
-  Bad: marketing a `~/.claude` draft as an npm dependency… Good: label it “local optional” and link once in README instead of pasting the blurb into five skills…
----
-
-# Maintain Skill Catalog
-
-## Dependencies
-
-- Required: none.
-- Conditional: `find-skills` when a dependency is external and the installation source is unknown.
-- Optional: `skill-creator` when extracting a repeated workflow into a new shared skill or heavily reshaping a skill.
-- Fallback: If an external dependency cannot be verified, **MUST** document unknowns honestly—**MUST NOT** invent package names, install commands, or skill aliases.
-
-## Non-negotiables
-
-- **MUST** read actual skill directories, validator scripts (`scripts/validate_*.py`, CI), `README.md`, and `agents/openai.yaml` patterns **before** reclassifying dependencies or rewriting catalog prose.
-- **MUST** treat each skill’s `## Dependencies` block as authoritative for skill-to-skill references; reconcile docs to match folders, not the reverse by guess.
-- **MUST** classify each dependency edge as: vendored-in-repo · local unpublished (not advertised as external) · external-with-install-guidance · alias-only (explain, don’t duplicate as separate dep).
-- **MUST NOT** duplicate skills or paste long prose into README without verifying whether a narrower edit or extraction fixes the repetition.
-- **MUST NOT** advertise a colleague’s unpublished `~/.codex/skills/...` name as if it were an npm-installable artifact unless verified.
-- After metadata or agent-config edits, **MUST** run **`apltk validate-skill-frontmatter`** and **`apltk validate-openai-agent-config`** (or fail the session with explanation if CLI unavailable)—**MUST NOT** declare the catalog consistent while validators fail.
-- If validator failures reveal a **systemic** gap, **MUST** prefer tightening the validator/CI in the **same** change set when appropriate, not only patching one skill ad hoc.
-
-## Standards (summary)
-
-- **Evidence**: Folders + scripts + frontmatter reality; optional `~/.codex/skills` spot-check for external names.
-- **Execution**: Inventory → classify → minimal focused edits → validate → report.
-- **Quality**: One skill one purpose; naming matches folder; agent configs synchronized.
-- **Output**: Updated lists/docs + green validators + explicit unknowns.
-
-## Workflow
-
-**Chain-of-thought:** Answer **`Pause →`** before moving to the next subsection; validator red **MUST** block “done.”
-
-### 1) Inventory
-
-- Enumerate top-level skill dirs (`SKILL.md` present); read touched `SKILL.md` files before inventing merges or new skills.
-- Read `README.md`, `AGENTS.md`/`CLAUDE.md`, and existing dependency notes.
-  - **Pause →** Is the requested change already satisfied by renaming or merging **existing** skill text instead of adding a sibling skill?
-  - **Pause →** Which validator script actually enforces description length and keys—did I open its source?
-
-### 2) Audit dependencies and conventions
-
-- Align `## Dependencies` across skills with shared vocabulary (`Required` / `Conditional` / `Optional` / `Fallback`).
-- Exact external strings only—verify spelling/plural vs installed tree.
-- Repeated workflows ⇒ prefer **extract** to new skill (`skill-creator`) over copy-paste.
-  - **Pause →** Would classifying dep X as “external” confuse installers—could it actually be repo-vendored or optional?
-
-### 3) Apply catalog edits
-
-- Minimal diffs; update `README` skill lists and external-dep sections **only when** inventory changed facts.
-- New shared skill: kebab-case folder = frontmatter `name`; add `agents/openai.yaml` following neighbors.
-  - **Pause →** Did I treat a **template** path under `references/` as a runtime skill—classification error?
-
-### 4) Validate
-
-- Run `apltk validate-skill-frontmatter` and `apltk validate-openai-agent-config`. If installer/discovery scripts changed behavior, smoke the paths they document.
-  - **Pause →** Any skill missing `agents/openai.yaml` or stale tool names—still acceptable for this repo’s rules?
-
-### 5) Report
-
-- Skills touched, conventions updated, external deps verified vs unknown; encode user-stated repo rules into skill or README so regressions recur less.
-
-## Sample hints
-
-- **Classification**: Skill A says `Conditional: Foo` but `Foo` lives only under `~/.claude/` unpublished → document as **local optional**, not “install Foo from npm.”
-- **Validator**: frontmatter `description` 1100 chars → expect **fail** if limit 1024—fix text, don’t disable check.
-- **Anti-pattern**: “We should mention skill X everywhere” → add **once** to README index + Dependencies of callers, not five duplicate paragraphs.

package/maintain-skill-catalog/agents/openai.yaml

@@ -1,4 +0,0 @@
-interface:
-  display_name: "maintain-skill-catalog"
-  short_description: "Audit and keep a skill repository consistent"
-  default_prompt: "Use $maintain-skill-catalog to audit top-level skills, classify internal versus external dependencies, sync catalog docs, extract repeated workflows into shared skills when justified, and run repository validators before finishing."