Skip to main content
Manusで任意のスキルを実行
ワンクリックで
GitHub リポジトリ

oh-my-openkei

oh-my-openkei には keibn29 から収集した 6 個の skills があり、リポジトリ単位の職業カバレッジとサイト内 skill 詳細ページを表示します。

収集済み skills
6
Stars
5
更新
2026-04-30
Forks
1
職業カバレッジ
2 件の職業カテゴリ · 100% 分類済み
リポジトリエクスプローラー

このリポジトリの skills

business-analyst
マネジメントアナリスト

Senior business analyst agent for market research, competitive analysis, requirements elicitation, and strategic planning. Use when analyzing business problems, documenting requirements, writing user stories, performing SWOT analysis, or converting ideas into product strategies. Triggers on tasks involving business analysis, requirements gathering, feasibility studies, or stakeholder interviews.

2026-04-30
backend-developer
ソフトウェア開発者

Senior backend developer (10+ years) obsessed with clean code and clean architecture. Specialized in Python/FastAPI with strict layered architecture (Repository → Service → API), dependency injection, SOLID principles, and production-grade patterns. Use when building APIs, designing database schemas, implementing services, writing repositories, or optimizing backend performance.

2026-04-29
karpathy-guidelines
ソフトウェア開発者

Inspired by Andrej Karpathy's observations on LLM coding pitfalls. Four principles: Think Before Coding, Simplicity First, Surgical Changes, Goal-Driven Execution. Use to improve code quality, reduce overcomplication, and avoid common LLM mistakes.

2026-04-29
vercel-react-best-practices
ソフトウェア開発者

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

2026-04-29
codemap
ソフトウェア開発者

Generate comprehensive hierarchical codemaps for UNFAMILIAR repositories. Expensive operation - only use when explicitly asked for codebase documentation or initial repository mapping

2026-04-29
simplify
ソフトウェア開発者

Simplifies code for clarity without changing behavior. Use for readability, maintainability, and complexity reduction after behavior is understood.

2026-04-29