notdefined

Generate and update notdefined YAML manifests from branding and metadata sources.

Updated Mar 28, 2026

Search Tags:#automation #branding #yaml #metadata #publication #showroom #notdefined

Ready to run

npx skills add https://github.com/rodacato/kwik-e-dev --skill notdefined

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: notdefined
Source: https://github.com/rodacato/kwik-e-dev/tree/main/plugins/launchpad/skills/notdefined
Command: npx skills add https://github.com/rodacato/kwik-e-dev --skill notdefined

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Notdefined.yml is the machine-readable contract for how a project card is rendered in the showroom. This skill automates creating or updating that file so the card accurately reflects branding, status, and links without manual editing.

Core Features & Use Cases

Generate or update .notdefined.yml from core branding and repository metadata (tagline, description, version, language, stack, status, and repo).
Validate consistency with branding assets and project source files, reducing drift between the repo and the showroom card.
Use when publishing a new project or refreshing an existing card that has stale tagline, status, or branding.

Quick Start

Use this skill to generate or update the showroom entry for the current project based on its branding and architecture docs.

Frequently Asked Questions about notdefined

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

FAQPage Schema

How do I generate a YAML manifest for showroom presentation from project metadata?▼

Generate a YAML manifest for showroom presentation by scanning branding and metadata sources like BRANDING.md, CLAUDE.md, and ARCHITECTURE.md to populate tagline, description, version, lang, stack, and status for accurate card rendering.

What's the best way to update a stale project card in a showroom?▼

Update a stale project card by refreshing the YAML manifest file that governs showroom presentation, validating consistency with branding assets and project source files to reduce drift between the repo and the rendered card.

What is a machine-readable YAML contract for rendering project cards?▼

A machine-readable YAML contract for rendering project cards is a configuration file that defines tagline, description, version, language, stack, status, repo URL, and branding asset references for accurate showroom display.

Does this showroom card generation require specific metadata files to work?▼

Showroom card generation scans BRANDING.md, CLAUDE.md, and ARCHITECTURE.md as core metadata sources to populate the YAML manifest, ensuring the rendered card accurately reflects branding, status, and links without manual editing.

When do I need to validate branding asset consistency for a showroom YAML file?▼

Validate branding asset consistency for a showroom YAML file when publishing a new project or refreshing an existing card that has stale tagline, status, or branding, reducing drift between the repository and the showroom presentation.