GitHub
requirements-gathering
Discovery questions, checklists, and techniques for gathering requirements. Use during discovery to ensure thorough understanding before creating issues.
☆ 4View skill
Lifestyle AI Skills
Discover Lifestyle skills, compare source repositories and read the instructions for each workflow.
Categories: Lifestyle
Lifestyle Clear filters
Browse skills
GitHub
code-review
Best practices for performing thorough, constructive code reviews. Use when reviewing PRs to ensure quality feedback that improves code and helps developers grow.
☆ 4View skill
GitHub
python-standards
Python coding standards, conventions, and best practices. Use when writing, reviewing, or testing Python code.
☆ 4View skill
GitHub
flutter-worktrees
Use when starting feature work that needs isolation from current workspace - creates isolated git worktrees with Flutter project setup
☆ 4View skill
GitHub
flutter-parallel-agents
Use when facing 2+ independent Flutter tasks that can be worked on without shared state or sequential dependencies
☆ 4View skill
GitHub
flutter-subagent-dev
Use when executing Flutter implementation plans with independent tasks in the current session
☆ 4View skill
GitHub
start-flutter-craft
Use when starting any conversation - establishes how to find and use Flutter development skills, requiring Skill tool invocation before ANY response including clarifying questions
☆ 4View skill
GitHub
design-polish
디자인 레퍼런스 기반 폴리싱. 트렌드 검색, Gap 분석, WCAG 접근성 체크, 개선안 도출. /design-polish 명령으로 실행.
☆ 4View skill
GitHub
flutter-debugging
Use when encountering any bug, test failure, or unexpected behavior in Flutter - requires systematic investigation before proposing fixes
☆ 4View skill
GitHub
flutter-finishing
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of Flutter development work by presenting structured options
☆ 4View skill
GitHub
flutter-executing
Use when you have a written implementation plan to execute with review checkpoints
☆ 4View skill
GitHub
flutter-verification
Use when about to claim work is complete, fixed, or passing - requires running Flutter verification commands and confirming output before making any success claims; evidence before assertions always
☆ 4View skill
GitHub
flutter-brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation using Clean...
☆ 4View skill
GitHub
flutter-planning
Use when you have a design or requirements for a multi-step Flutter feature, before touching code
☆ 4View skill
GitHub
flutter-testing
Use when writing tests for Flutter code - follows priority-based testing (Repository → State → Widget) after implementation
☆ 4View skill
GitHub
flutter-review-receive
Use when receiving code review feedback - requires technical evaluation and verification, not performative agreement or blind implementation
☆ 4View skill
GitHub
flutter-project-init
Creates a new Flutter project with Clean Architecture, domain pattern boilerplate, and production-ready setup
☆ 4View skill
GitHub
flutter-writing-skills
Use when creating new skills for flutter-craft or editing existing skills
☆ 4View skill
GitHub
flutter-review-request
Use when completing tasks, implementing major features, or before merging to verify Flutter code meets requirements
☆ 4View skill
GitHub
tailscale
Manage Tailscale VPN, Serve, and Funnel from the CLI.
☆ 4View skill
GitHub
gh
GitHub CLI for repos, PRs, issues, and Actions.
☆ 4View skill
GitHub
dashlane
Dashlane CLI for vault access and automation.
☆ 4View skill
GitHub
eufy
Manage Eufy Security (HomeBase S380 + SoloCam S340/E340) from the `eufy` CLI—capture snapshots, forward alarms to the Tuya hub, and change guard/alarm modes through eufy-security-ws.
☆ 4View skill
GitHub
tuya
Control Tuya devices via local Home Assistant (tuya-local) or Tuya Cloud using the tuya-hub Go CLI.
☆ 4View skill
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.