agentleFS
ww-w-aiww-w-ai/bkit-codex/.agents/skills/starter/SKILL.md

starter

Skill69 starsChanged 8 months agoApache-2.0View on GitHub

Static web development guide for beginners. Covers HTML/CSS/JavaScript and Next.js App Router basics. Project initialization with "init starter". Triggers: static website, portfolio, landing page, HTML CSS, beginner, 정적 웹, 포트폴리오, 초보자, 静的サイト, 初心者, 静态网站, 初学者, sitio web estático, site statique, statische Website, sito web statico Do NOT use for: fullstack apps (use $dynamic), enterprise (use $enterprise).

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create project directory structure (HTML/CSS/JS or Next.js)

    line 26
  2. Distinctive:

    Create AGENTS.md (Level: Starter specified)

    line 28
  3. Distinctive:

    Create docs/ folder structure (for PDCA documents)

    line 29
  4. Distinctive:

    No login/registration (requires server)

    line 186
  5. Distinctive:

    No data storage (requires database)

    line 187
  6. Distinctive:

    No admin pages (requires backend)

    line 188
  7. Distinctive:

    No payment features (requires backend)

    line 189

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Beginner (Starter) Skill

Static web development for beginners and non-developers.

Actions

ActionDescriptionExample
initProject initialization$starter init my-portfolio
guideDisplay development guide$starter guide
helpBeginner help$starter help

init (Project Initialization)

  1. Create project directory structure (HTML/CSS/JS or Next.js)
  2. Generate package.json (when Next.js selected)
  3. Create AGENTS.md (Level: Starter specified)
  4. Create docs/ folder structure (for PDCA documents)
  5. Initialize .pdca-status.json

guide (Development Guide)

  • Analyze current project state
  • Suggest next steps appropriate for Starter level
  • Phase 1-3 focused Pipeline guide (1 -> 2 -> 3 -> 6 -> 9)

help (Beginner Help)

  • Explain HTML/CSS/JS basic concepts
  • Answer frequently asked questions
  • Provide example code

Target Audience

  • Those learning programming for the first time
  • Those who want to create a simple website
  • Those who need a portfolio site

Tech Stack

Option A: Pure HTML/CSS/JS (For Complete Beginners)

HTML5        -> Web page structure
CSS3         -> Styling
JavaScript   -> Dynamic features (optional)

Option B: Next.js (Using Framework)

Next.js 14+  -> React-based framework
Tailwind CSS -> Utility CSS
TypeScript   -> Type safety (optional)

Language Tier Guidance

Recommended: Tier 1 languages only (Python, TypeScript, JavaScript)

TierAllowedReason
Tier 1YesFull AI support, Vibe Coding optimized
Tier 2LimitedConsider Dynamic level instead
Tier 3-4NoUpgrade to Dynamic/Enterprise

Project Structure

Option A: HTML/CSS/JS

project/
├── index.html          # Main page
├── about.html          # About page
├── css/
│   └── style.css       # Styles
├── js/
│   └── main.js         # JavaScript
├── images/             # Image files
├── docs/               # PDCA documents
│   ├── 01-plan/
│   └── 02-design/
└── README.md

Option B: Next.js

project/
├── src/
│   ├── app/
│   │   ├── layout.tsx      # Common layout
│   │   ├── page.tsx        # Main page
│   │   └── about/
│   │       └── page.tsx    # About page
│   └── components/         # Reusable components
├── public/                 # Static files
├── docs/                   # PDCA documents
├── package.json
├── tailwind.config.js
└── README.md

Core Concepts

HTML (Web Page Structure)

<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>My Website</title>
    <link rel="stylesheet" href="css/style.css">
</head>
<body>
    <header>Header</header>
    <main>Main content</main>
    <footer>Footer</footer>
</body>
</html>

CSS (Styling)

body {
    font-family: 'Inter', sans-serif;
    margin: 0;
    padding: 0;
}

.container {
    max-width: 1200px;
    margin: 0 auto;
    padding: 20px;
}

@media (max-width: 768px) {
    .container { padding: 10px; }
}

Next.js App Router

// app/page.tsx
export default function Home() {
  return (
    <main className="container mx-auto p-4">
      <h1 className="text-3xl font-bold">Welcome!</h1>
    </main>
  );
}

Deployment Methods

GitHub Pages (Free)

  1. Create GitHub repository
  2. Push code
  3. Settings -> Pages -> Source: main branch
  4. Access at https://username.github.io/repo-name

Vercel (Recommended for Next.js)

  1. Sign up at vercel.com (GitHub integration)
  2. "New Project" -> Select repository
  3. Click "Deploy"

Limitations

  • No login/registration (requires server)
  • No data storage (requires database)
  • No admin pages (requires backend)
  • No payment features (requires backend)

When to Upgrade

Move to Dynamic Level ($dynamic) if you need:

  • Login functionality
  • Data storage
  • Admin page
  • User communication features

Pipeline Flow (Starter)

Phase 1 -> 2 -> 3 -> 6(static) -> 9

Skip API (Phase 4), Design System (Phase 5 optional), SEO only in Phase 7.

Common Mistakes

MistakeSolution
Image not showingCheck path (./images/photo.jpg)
CSS not appliedCheck link tag path
Page navigation not workingCheck href path (./about.html)
Broken on mobileCheck <meta name="viewport"> tag

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.