Search

PythonReactSEOPDF

raydocs AI Skills

GitHub ↗

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

Author statistics

Indexed skills

39

Repository stars across indexed skills

6

Repository forks

0

Average repository stars per indexed skill

0

Repository stars may repeat across skills from the same repository.

39 skills

Browse skills

GitHub

flow-next

raydocs

Manage Flow task tracking in .flow/ directory. Use when user asks to show tasks, list epics, add a task, create a task, check what's ready, view task status, or show a specific task ID like fn-1-abc. NOT for pl...

GitHub

flow-plan

raydocs

Plan and design feature implementations with structured task breakdown and acceptance criteria. Use when user wants to plan a feature, design an implementation, create an epic with tasks, or turn an idea into a...

GitHub

flow-work

raydocs

Execute implementation tasks systematically with git setup, task tracking, quality checks, and commit workflow. Use when user wants to implement a plan, work through a spec, execute tasks from an epic, or build...

GitHub

context-scout

raydocs

Token-efficient codebase exploration using RepoPrompt codemaps and slices. Use when you need deep codebase understanding without bloating context, finding all pieces of a feature across many files, or building...

GitHub

repo-scout

raydocs

Scan repository to find existing patterns, conventions, and related code paths for a feature or change. Use when you need to understand codebase conventions, find similar implementations, or identify reusable c...

GitHub

flow-gap-analyst

raydocs

Map user flows, edge cases, and missing requirements from a brief spec. Use when you need to find what is missing or ambiguous in a feature request before implementation starts.

GitHub

flow-interview

raydocs

Conduct in-depth interviews to extract complete implementation details for features, epics, or tasks. Use when user wants to flesh out a spec, refine requirements, clarify a feature before building, or explore...

GitHub

flow-impl-review

raydocs

Review code implementations for quality, security, and architectural soundness. Use when reviewing code changes, PRs, or implementations. Conducts John Carmack-level review examining correctness, simplicity, ed...

GitHub

practice-scout

raydocs

Gather modern best practices and pitfalls for a specific implementation task. Use when you need current guidance on how to implement a feature correctly, avoid common mistakes, or find real-world examples from...

GitHub

docs-scout

raydocs

Find the most relevant framework and library documentation pages for implementing a feature correctly. Use when you need official API references, version-specific guidance, or examples from documentation.

GitHub

docs-gap-scout

raydocs

Identify documentation that may need updates based on planned changes. Use when planning a feature to identify which docs (README, CHANGELOG, API docs) will need updates after implementation.

GitHub

flow-example

raydocs

Example skill demonstrating Flow-Next path resolution strategy and Factory skill format. Use this as a template for creating new Factory skills that integrate with flowctl.

GitHub

github-scout

raydocs

Search GitHub repositories (public and private) for code patterns, implementations, and examples. Use when you need to find how others implement a feature, search for code patterns across repos, or find known i...

GitHub

flow-plan-review

raydocs

Review implementation plans with Carmack-level rigor before coding. Use when reviewing Flow epic specs, design docs, or when user wants a thorough plan review. Examines architecture, feasibility, edge cases, an...

GitHub

epic-scout

raydocs

Scan existing epics to find dependencies and relationships for a new plan. Use when planning a new feature to identify if it depends on or conflicts with existing work.

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.