skills/bityoungjae/project-scaffolder/SKILL.md
Creates plan.md, task.md, persona.md, project-context.md, and CLAUDE.md for new self-learning resource projects. Use when: (1) /init command is invoked, (2) setting up a new tutorial/guide/documentation project, (3) structure-designer agent needs templates for learning resource structure design. Provides hierarchical Part/Chapter/Section templates with page allocation.
npx skillsauth add aiskillstore/marketplace project-scaffolderInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill provides templates and guidance for scaffolding new self-learning resource projects.
The following templates are available in this skill directory:
| Template | Purpose | |----------|---------| | plan-template.md | Project structure with Part/Chapter/Section hierarchy | | task-template.md | Session-based task checklist mirroring plan.md | | persona-template.md | Writer/Reader persona and code policy definitions | | project-context-template.md | Target environment and reference URLs | | claude-md-template.md | CLAUDE.md project instructions |
Before scaffolding, collect the following information:
plan.md - Main structure document (use plan-template.md)task.md - Session-divided checklist (use task-template.md)persona.md - Writer/Reader definitions (use persona-template.md)project-context.md - Environment and references (use project-context-template.md)CLAUDE.md - Project instructions for Claude (use claude-md-template.md)| Content Type | Percentage | |--------------|------------| | Introduction/Overview | 5-8% | | Core Content | 60-70% | | Practice/Examples | 20-25% | | Summary/Review | 5-8% |
When creating task.md, divide work into Claude Code sessions:
<!-- Session 1: Part 1 Foundations -->
- [ ] 1.1 Introduction (8p)
- [ ] 1.2 Core Concepts (7p)
<!-- Session 2: Part 1 Architecture -->
- [ ] 1.3 System Design (10p)
Use {VARIABLE_NAME} format for all placeholders:
| Variable | Description |
|----------|-------------|
| {PROJECT_TITLE} | Project name |
| {TARGET_SYSTEM} | Target OS/environment |
| {TARGET_AUDIENCE} | Reader experience level |
| {TOTAL_PAGES} | Total estimated pages |
| {DATE} | Creation/update date |
| {PART_TITLE} | Part title |
| {CHAPTER_TITLE} | Chapter title |
| {SECTION_TITLE} | Section title |
| {PAGES} | Page count for section |
Before completing scaffolding, verify:
{VARIABLE_NAME} formatdevelopment
Apple Human Interface Guidelines for content display components. Use this skill when the user asks about charts component, collection view, image view, web view, color well, image well, activity view, lockup, data visualization, content display, displaying images, rendering web content, color pickers, or presenting collections of items in Apple apps. Also use when the user says how should I display charts, what's the best way to show images, should I use a web view, how do I build a grid of items, what component shows media, or how do I present a share sheet. Cross-references: hig-foundations for color/typography/accessibility, hig-patterns for data visualization patterns, hig-components-layout for structural containers, hig-platforms for platform-specific component behavior.
tools
Automate HelpDesk tasks via Rube MCP (Composio): list tickets, manage views, use canned responses, and configure custom fields. Always search tools first for current schemas.
testing
Expert Haskell engineer specializing in advanced type systems, pure functional design, and high-reliability software. Use PROACTIVELY for type-level programming, concurrency, and architecture guidance.
tools
GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.