fpf-skilldesign-mint-name

venikman's avatarfrom venikman

Generated skill for design/mint-name.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 10, 2026
[Brand and Creative Direction]

When & Why to Use This Skill

The fpf-skill:design-mint-name is a specialized tool that automates the F.18 Name Card process from the First Principles Framework (FPF). It is designed to 'mint' high-quality names for concepts, artifacts, and repositories, ensuring they possess high semantic fidelity and cognitive ergonomics. By utilizing a rigorous 7-step semantic read-through and a matrix-based evaluation, this skill helps teams move beyond arbitrary naming toward a structured, logical, and descriptive nomenclature system.

Use Cases

  • Naming new software repositories or microservices to ensure the technical ID and plain English label accurately reflect their strict function.
  • Developing precise terminology for new architectural components or internal tools to maintain linguistic consistency across engineering teams.
  • Validating proposed product or feature names against semantic 'sense-seeds' to identify if a name is too narrow, too wide, or conceptually flawed.
  • Creating standardized 'Name Cards' that document the context, purpose, and minimal definitional statement (MDS) for organizational artifacts.
  • Refining technical documentation by replacing ambiguous jargon with 'minted' names that have been tested for cognitive ergonomics.
namefpf-skill:design-mint-name
descriptionGenerated skill for design/mint-name.
version0.1.0
allowed_tools[]

design/mint-name Kernel

Context

This skill enacts the F.18 Name Card process from the First Principles Framework (FPF). It is used to "mint" new names for concepts, artifacts, or repositories ensuring high semantic fidelity and cognitive ergonomics.

Metadata

  • ID: fpf-skill:design-mint-name
  • Pattern Ref: F.18 (Name Card)
  • Role: Namer
  • Version: 0.1.0

Instructions

Step 1: Define the Context

  1. Identify the Bounded Context: Where does this name live? (e.g., "Skill Repo", "Runtime Kernel").
  2. State the Purpose: What is the strict function of the thing being named?

Step 2: Generate Candidates

Propose 3-5 candidates. For each, define:

  • Twin Labels: Technical ID (kebab-case) and Plain English.
  • Minimal Definitional Statement (MDS): A strict definition of what the thing IS.

Step 3: Run P2 Semantic Read-Through

For each candidate, test it against the 7 standard FPF sense-seeds (S1–S7):

  • S1 Add: "Add a new <Thing>..."
  • S2 Retrieve: "Get a <Thing> from..."
  • S3 Teach: "Teach the concept of <Thing>..."
  • S4 Provenance: "Trace the <Thing> back to..."
  • S5 Relations: "Link <Thing> to..."
  • S6 Rep-Change: "Change format of <Thing>..."
  • S7 Non-Native: "Add a foreign <Thing>..."

Step 4: Tally the Matrix

Mark each test as:

  • TN: Too Narrow
  • OT: On Target
  • TW: Too Wide
  • WP: Wrong Prototype

Step 5: Mint the Card

Select the candidate with the highest OT count (and 0 WP). Output the final Name Card in Markdown format.

F.18 Name Card Template

A minted name card must include:

  • CardMode: (e.g. MintNew)
  • Row ID: (e.g. RN.FPF.SKILLREPO.001)
  • Context of Meaning
  • Kind
  • Purpose / use-domain
  • Minimal Definitional Statement (MDS)
  • Didactic subtitle
  • Sense reference
  • Archetypal situations (sense-seeds)
  • P2 Matrix Tally