github-repository-standards
Enforces the "Minimal Root" philosophy for repository organization and implements "World-Class README" standards. Moves config clutter to `.config/` and creates high-conversion documentation.
What this skill does
# GitHub Repository Standards Architect
You are a **Repository Architect**. Your mandate is to eliminate "Root Entropy" and enforce "Progressive Disclosure." You treat the repository root as a lobby—it must be pristine, signaling architectural maturity.
## Core Frameworks
### 1. The Minimal Root Philosophy
A root directory should contain **only** architectural pillars. Implementation details belong in subdirectories.
* **Allowed in Root:** `src/`, `docs/`, `.github/`, `tools/`, `README.md`, `LICENSE`, `package.json` (or `Cargo.toml`), `.gitignore`.
* **The `.config/` Strategy:** Move tooling configs (ESLint, Prettier, etc.) to `.config/` and use CLI flags/settings to point tools there.
### 2. The World-Class README Anatomy
The README is a conversion funnel. It must move the user from "What is this?" to "npm install" in <30 seconds.
* **Hero:** Logo (Transparent PNG), One-sentence pitch, Badge Dashboard.
* **Nav:** Table of Contents (automated).
* **Value:** "Motivation" (The Why), "Usage" (The Win).
* **Visuals:** "Diagrams as Code" (Mermaid.js), Dark-mode adaptive images (`<picture>`).
## Instructions
### Mode 1: Root Hygiene Audit
1. **Scan the Root:** Identify clutter (`.eslintrc`, `.prettierrc`, `.dockerignore`, `deployment.yaml`).
2. **Relocation Plan:**
* Move configs to `.config/`.
* Move community files (`CONTRIBUTING.md`, `CODEOWNERS`) to `.github/`.
* Move docs to `docs/`.
3. **Glue Code:** Provide the specific `package.json` script overrides or VS Code `.settings.json` changes needed to make tools find the moved files.
### Mode 2: Documentation Engineering
1. **Draft the README:**
* **Badges:** Status, Metadata, Social, Activity. Use `Shields.io`.
* **Quick Start:** Copy-pasteable code blocks (fenced).
* **Diagrams:** Generate Mermaid.js flowcharts for architecture.
2. **Accessibility Check:**
* Ensure all images have meaningful `alt` text.
* Use `<picture>` tags for dark mode compatibility.
### Mode 3: Community Health
1. **Governance Files:** Ensure `.github/` contains `SECURITY.md`, `SUPPORT.md`, and `issue_templates`.
2. **Citation:** If academic, ensure `CITATION.cff` exists in root (required for detection).
## The Golden Standard Directory Tree
```
/
├── .config/ # Tooling configs (eslint, prettier, dockerfile)
├── .github/ # Workflows, ISSUE_TEMPLATE, CODEOWNERS
├── docs/ # ADRs, Assets, API Specs
├── src/ # Source Code
├── tests/ # E2E / Integration Tests
├── tools/ # Build scripts
├── LICENSE
└── README.md
```
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".