fpf-authoring-conventions-style-guide

Codify FPF Authoring Conventions and Style Guide E.8 for pattern documentation.

Updated Jan 11, 2026
One-click install
npx skills add https://github.com/venikman/fpf-foundry --skill fpf-authoring-conventions-style-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fpf-authoring-conventions-style-guide
Source: https://github.com/venikman/fpf-foundry/tree/main/design/skills/knowledge/fpf-authoring-conventions-style-guide
Command: npx skills add https://github.com/venikman/fpf-foundry --skill fpf-authoring-conventions-style-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill codifies the FPF Authoring Conventions and Style Guide (E.8) to standardize how patterns are written, reviewed, and taught, reducing drift and fragmentation across artifacts.

Core Features & Use Cases

  • Canonical Pattern Template: Enforces a uniform 1–13 section structure, ensuring readability and teachability.
  • Archetypal Grounding & Bias‑Annotation: Provides explicit System/Episteme grounding and cross‑discipline lenses for clear evaluation.
  • Conformance Checklist & SoTA Echoing: Embeds verifiable criteria and keeps SoTA alignment visible for audit and learning.
  • Education & Review Utility: Helps pattern authors produce consistent, high-quality documentation for teams and onboarding.

Quick Start

Read this style guide and apply E.8 to new patterns when authoring or reviewing artifacts; ensure sections, grounding, and conformance sections are present.

Frequently Asked Questions about fpf-authoring-conventions-style-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the FPF authoring style guide for pattern documentation?

The FPF authoring style guide is a standardized convention set enforcing a uniform 1 to 13 section structure to ensure consistent pattern documentation, readability, and teachability across artifacts.

How do I write documentation using a pattern style guide?

Apply the E.8 style guide to your pattern documentation by ensuring all required sections, archetypal grounding, bias annotation, and conformance checklists are present during authoring and review.

What's the best way to check pattern conformance during a review?

The best way to check pattern conformance is using an embedded conformance checklist that verifies required sections, System and Episteme grounding, and State of the Art alignment visibility.

Does the FPF style guide require external tools for bias annotation?

No, the FPF style guide requires no external tools to implement archetypal grounding and bias annotation. It operates as a standalone reference articulating evaluation criteria for pattern artifacts.

Why does my pattern documentation lack consistent structure across teams?

Pattern documentation lacks consistent structure due to drift and fragmentation across artifacts. Applying a unified canonical pattern template resolves this by enforcing a standard 1 to 13 section structure.

When do I need to use archetypal grounding in pattern authoring?

You need archetypal grounding in pattern authoring whenever creating or reviewing artifacts to provide explicit System and Episteme grounding and cross discipline lenses for clear evaluation.