senternet-site-init

Generates AGENTS.md, CLAUDE.md, and README.md documentation for completed Vite or Next.js sites.

Updated May 8, 2026
One-click install
npx skills add https://github.com/MattSenter/senternet-site-skills --skill senternet-site-init-mattsenter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: senternet-site-init
Source: https://github.com/MattSenter/senternet-site-skills/tree/main/.claude/skills/senternet-site-init
Command: npx skills add https://github.com/MattSenter/senternet-site-skills --skill senternet-site-init-mattsenter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Completed marketing sites often ship without documentation, leaving future developers and AI agents without context on architecture decisions, build pipelines, and deployment workflows. This Skill analyzes the actual codebase and writes accurate project documentation instead of placeholder templates. ## Core Features & Use Cases - Codebase Analysis: Reads package.json, routing files, Firebase configs, env files, and build scripts to extract real project values. - Three-File Generation: Produces AGENTS.md (comprehensive agent context), CLAUDE.md (pointer to AGENTS.md), and README.md (human-facing overview with scripts table and quick start). - Framework Detection: Detects Vite vs Next.js tracks via .site-framework.json and documents the correct architectural rules for each (hydrateRoot and prerendering vs server components and App Hosting). - Use Case: After finishing a Firebase-hosted marketing site, run this Skill to generate documentation that captures the three-file routing rule, environment variables, and deploy commands so the next contributor avoids known traps. ## Quick Start Ask the AI to generate AGENTS.md, CLAUDE.md, and README.md documentation for the completed site in the current project directory.

Frequently Asked Questions about senternet-site-init

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

FAQPage Schema
How do I generate AGENTS.md and README.md for an existing project?▼

Run this Skill in the project root and it reads package.json, routing files, Firebase configs, and env files to write AGENTS.md, CLAUDE.md, and README.md with real values. No placeholders are used; every script, domain, and project name comes from the actual codebase.

What files should document a Vite React Firebase site?▼

Three files cover it: AGENTS.md for comprehensive AI agent context including architectural traps like hydrateRoot and the three-file routing rule, CLAUDE.md pointing to AGENTS.md, and README.md with quick start, scripts table, and deploy commands.

Does this documentation workflow support Next.js projects?▼

Yes, the Skill detects the framework from .site-framework.json and switches tracks. For Next.js it documents App Router conventions, server components, apphosting.yaml environment variables, and the one-file page-add rule instead of Vite prerendering rules.

Why does generated documentation sometimes contain wrong framework details?▼

Wrong-track docs happen when Vite conventions like hydrateRoot or prerender arrays are applied to a Next.js project. This Skill checks .site-framework.json first and replaces the entire architectural decisions section to match the detected framework.

What is the three-file rule for adding routes?▼

On the Vite track, every new page must be added to src/App.tsx, scripts/prerender.mjs, and scripts/generate-sitemap.mjs together. Missing any one leaves the page without static HTML for crawlers or without a sitemap entry.