Search

PythonReactSEOPDF

Young-Z AI Skills

GitHub ↗

Browse published AI skills maintained by Young-Z. Compare skill descriptions and follow each source repository for setup instructions.

Author statistics

Indexed skills

22

Repository stars across indexed skills

176

Repository forks

44

Average repository stars per indexed skill

8

Repository stars may repeat across skills from the same repository.

22 skills

Browse skills

GitHub

task-type-ideation

Young-Z

Learn and refine user ideas through brainstorming. Use when user uploads idea files to the Workplace. Analyzes uploaded content, asks clarifying questions, and produces structured idea summary. Triggers on requ...

GitHub

feature-stagefeature-board-management

Young-Z

Manage feature lifecycle in docs/planning/features.md. Category-level skill called during Step 4 (Category Closing) for feature-stage tasks. Accepts Task Data Model with feature_id and feature_phase, updates fe...

GitHub

task-execution-guideline

Young-Z

Execute development tasks with planning and tracking. Triggers on requests like "implement feature", "fix bug", "create PR", "design architecture", "set up project". Provides 6-step workflow for task planning,...

GitHub

task-type-doc-viewer

Young-Z

Generate a web-based documentation viewer for browsing project docs. Use when human wants to view documentation in a web browser. Triggers on requests like "create doc viewer", "documentation viewer", "browse d...

GitHub

ideation-stageideation-board-management

Young-Z

Manage idea tracking during ideation-stage tasks. This is a category-level skill called during Step 4 (Category Closing) for ideation-stage tasks. Accepts Task Data Model. Outputs category_level_change_summary.

GitHub

git-version-control

Young-Z

Manage git version control operations including repository initialization, staging, committing, and GitHub integration. Provides standardized .gitignore templates and structured commit messages. Use for version...

GitHub

task-type-dev-environment

Young-Z

Set up development environment with appropriate tech stack (Python with uv or Node.js with npm/yarn), project structure, and git version control. Use when initializing project environments or preparing workspac...

GitHub

requirement-stagerequirement-board-management

Young-Z

Manage requirement tracking during requirement-stage tasks. This is a category-level skill called during Step 4 (Category Closing) for requirement-stage tasks. Accepts Task Data Model. Outputs category_level_ch...

GitHub

task-type-feature-refinement

Young-Z

Refine feature specification for a single feature. Queries feature board for context, creates/updates specification document. Use when a feature needs detailed requirements. Triggers on requests like "refine fe...

GitHub

task-type-share-idea

Young-Z

Convert refined idea summaries to shareable document formats (PPTX, DOCX, PDF). Use when user wants to share or present an idea. Uses MCP document conversion tools or pandoc. Triggers on requests like "share id...

GitHub

task-board-management

Young-Z

Manage task boards for tracking development work. This is a MANDATORY skill called during Step 4 (Category Closing) of the task lifecycle. Accepts Task Data Model as input. Provides operations for task board CR...

GitHub

task-type-technical-design

Young-Z

Create technical design for a single feature. Queries feature board, reads specification, designs solution with KISS/YAGNI/DRY principles. Creates two-part design document. Triggers on requests like "design fea...

GitHub

task-type-project-init

Young-Z

Initialize a new project with standard folder structure and documentation. Use when starting a fresh project or onboarding to existing project. Triggers on requests like "init project", "start new project", "se...

GitHub

task-type-code-implementation

Young-Z

Implement code based on technical design for a single feature. First queries feature board, then learns technical design (and architecture if referenced). Follows TDD workflow and KISS/YAGNI principles. Trigger...

GitHub

task-type-change-request

Young-Z

Process change requests by analyzing impact on existing requirements and features. Determines if CR modifies existing feature (→ refinement) or requires new feature (→ requirement update + feature breakdown). T...

GitHub

task-type-feature-breakdown

Young-Z

Break requirements into high-level features and create feature list in requirement-details.md. Calls feature-board-management to initialize feature tracking. Use when requirements are gathered and need to be sp...

GitHub

task-type-requirement-gathering

Young-Z

Gather requirements from user requests and create requirement summary. Use when starting a new feature or receiving a new user request. Triggers on requests like "new feature", "add feature", "I want to build",...

GitHub

task-type-bug-fix

Young-Z

Diagnose and fix bugs in existing code. Use when something is broken, not working as expected, or producing errors.

GitHub

task-type-human-playground

Young-Z

Create interactive examples for human validation. Use when code is implemented and ready for human testing. Provides procedures for creating demos, documentation, and test scenarios.

GitHub

task-type-test-generation

Young-Z

Generate comprehensive test cases from technical design before implementation. Follows TDD approach - write tests first, then implement. Queries feature board, reads technical design, creates all test files. Us...

GitHub

task-type-feature-closing

Young-Z

Close completed feature and create pull request. Use when human has validated the playground and feature is ready to ship. Provides procedures for final verification, PR creation, and documentation.

GitHub

task-type-user-manual

Young-Z

Create or update the user manual (README.md) with instructions on how to install, configure, and run the application. Use when minimum features are implemented or when specifically asked to document how to run...

The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.