pattern-language-as-agent-skill git:20261018.b2b1b02A

Immutable. This exact content never changes and is served at /api/v1/blob/8be2a78013ce1967.

---
name: pattern-language-as-agent-skill
description: |
  Compacted runtime projection of the Pattern Language as Agent Skill (PLAS) LPF.
  Author and improve a Domain Principle Framework (DPF) or Local Practices Framework
  (LPF) directly in Agent-skill form (SKILL.md + references/). Use when creating,
  revising, or maintaining a DPF/LPF as a skill, or when the user mentions
  "pattern language as agent skill". Depends on fpf-core.
---

# Pattern Language as Agent Skill (PLAS) — compacted projection

**Depends on:** `fpf-core` (governing method FPF); `agent-skill-builder` (carrier mechanics); `episteme-compaction` (for `PLAS.CompactedProjection`)
**Bounded context:** authoring, using, and evolving a DPF or LPF whose sole carrier is an Agent skill
**Source & readiness:** a representation of the canonical carrier at `<project>/skills/pattern-language-as-agent-skill/` (it owns the graph and provenance); readiness (collective): `source-faithful` — compacted profile, not `case-validated`

## When to load which pattern

| Situation | Load |
|---|---|
| Deciding whether and what to author as a DPF-skill (cold start) | `references/PLAS.EntryRoute.md` |
| Setting up the skill directory layout and the single-surface decision | `references/PLAS.SkillLayout.md` |
| Writing SKILL.md as a routing-only dispatcher | `references/PLAS.Dispatcher.md` |
| Writing one pattern body in references/ | `references/PLAS.PatternBody.md` |
| Recording a card's FPF dependencies (frontmatter) | `references/PLAS.GoverningCues.md` |
| Naming the skill and PatternIDs | `references/PLAS.Naming.md` |
| Evaluating, improving, refreshing a DPF-skill | `references/PLAS.QualityAndRefresh.md` |
| Authoring a DPF-skill with no FPF dependency (self-sufficient variant) | `references/PLAS.SelfSufficient.md` |
| Authoring/evaluating a compacted (minified) runtime projection | `references/PLAS.CompactedProjection.md` |

## Navigation rule

First load `references/PLAS.EntryRoute.md` — it decides whether a DPF-skill is the right outcome and fixes the authoring scenario (FPF-grounded vs self-sufficient; from-scratch vs external-standard). Then `references/PLAS.SkillLayout.md` for the single-surface decision and directory layout, then the mechanics cards (`PLAS.Dispatcher` → `PLAS.PatternBody` → `PLAS.GoverningCues` → `PLAS.Naming`), closing with `PLAS.QualityAndRefresh`. The self-sufficient variant routes to `PLAS.SelfSufficient`; a deliberately minified carrier routes to `PLAS.CompactedProjection`.

## Lookup rules

- **Index first, then "no".** Before looking for a pattern, check `references/INDEX.md`. If the id is not listed there, the pattern does not exist — answer "no"; do not open files searching for it.
- **Read once.** Do not reopen a file you have already read — reuse its already-read content from your context.

## Single surface

`references/` is the canonical surface of this projection. No `assets/` monolith and no reader-facing publication form exists. This skill is a **representation** of the full PLAS carrier, not the carrier itself; the dependency graph and provenance live in the canonical source.

## Guardrails

When a judgment is ambiguous — dropping or widening source content, placing an attachment, renaming a marker, or any choice that could diverge from the owner's intent — **ask the owner before acting**. Deployment is owner-owned: the authoring agent edits only the repo carrier; the installed copy is synced exclusively by the owner.