j5ik2o/okite-ai

This repository also configures its own agents. See what okite-ai tells them →

81Stars on the repository
78Mods indexed here, across every type
4mo agoLast push, which is what freshness is scored on
MITLicence, which decides whether bodies are shown

j5ik2o/okite-ai

Skill Claude CodeCodex

Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.

not rated 81 4mo ago A 31 tokens copy · 100% MIT

j5ik2o/okite-ai

Skill Claude CodeCodex

Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.

not rated 81 4mo ago A 31 tokens copy · 88% MIT

openspec-explore

27

j5ik2o/okite-ai

Skill Claude CodeCodex

Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.

not rated 81 4mo ago A 39 tokens copy · 92% MIT

openspec-propose

28

j5ik2o/okite-ai

Skill Claude CodeCodex

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

not rated 81 4mo ago A 47 tokens copy · 100% MIT

package-design

29

j5ik2o/okite-ai

Skill Claude CodeCodex

A design guide for arranging packages and modules around responsibilities, dependencies, and the reasons code is likely to change.

not rated 81 4mo ago A 157 tokens original MIT

parse-dont-validate

30

j5ik2o/okite-ai

Skill Claude CodeCodex

A code-review and design approach that replaces checks which merely report valid or invalid data with typed values that carry the result of the check.

not rated 81 4mo ago A 185 tokens original MIT

j5ik2o/okite-ai

Skill Claude CodeCodex

An implementation guide for building CQRS systems, which separate changing data from reading it, and event sourcing systems, which record changes as events, with Apache Pekko and Scala 3.

not rated 81 4mo ago A 368 tokens original MIT

pr-green

32

j5ik2o/okite-ai

Skill Claude CodeCodex

A workflow for making a GitHub pull request ready to merge by investigating failed automated checks and related issues, then fixing and verifying them.

not rated 81 4mo ago A 271 tokens original MIT

j5ik2o/okite-ai

Skill Claude CodeCodex

A refactoring workflow for reorganizing a codebase's packages and modules, which are folders or code units grouped by responsibility.

not rated 81 4mo ago A 156 tokens original MIT

repository-design

34

j5ik2o/okite-ai

Skill Claude CodeCodex

A guide for designing repositories around domain aggregates, which are groups of related business objects changed as one unit.

not rated 81 4mo ago A 240 tokens original MIT

j5ik2o/okite-ai

Skill Claude CodeCodex

A clean-architecture guide for deciding where repository interfaces belong. A repository is the part of an application that describes saving and retrieving domain data.

not rated 81 4mo ago A 176 tokens original MIT

reviewing-skills

36

j5ik2o/okite-ai

Skill Claude CodeCodex

A review tool for Claude Code skills, which are reusable instructions for an AI coding assistant. It checks their files, structure, wording, examples, and workflow against recommended practices.

not rated 81 4mo ago A 108 tokens original MIT

tell-dont-ask

37

j5ik2o/okite-ai

Skill Claude CodeCodex

A code-design approach that gives an object commands to perform its own work instead of reading its internal state and making decisions elsewhere.

not rated 81 4mo ago A 212 tokens original MIT

j5ik2o/okite-ai

Skill Claude CodeCodex

A language-independent design guide for deciding when basic values such as strings or numbers should be wrapped in named domain types. A domain type represents a concept with its own rules, such as an email address or money amount.

not rated 81 4mo ago A 275 tokens original MIT

At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: