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

ore-ai-web

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

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

このリポジトリの skills

library-docs
ソフトウェア開発者

Use this skill when a task depends on a library or dependency and you need reliable documentation or API context. Prefer project instructions, repo-local skills, global skills, installed docs, source, and types first. Use remote docs only when local material is not enough to complete the task safely.

2026-03-27
typescript
ソフトウェア開発者

Practical TypeScript defaults for application code: strong but simple typing, clear type modeling, consistent `type` vs `interface` choices, and keeping shared/exported types in nearby `types.ts` files. Use when writing or refactoring TypeScript and deciding how to model data, annotate boundaries, organize type definitions, or improve readability without adding type noise.

2026-03-27
typescript-fullstack-organization
ソフトウェア開発者

Organize or refactor modern TypeScript fullstack applications around module-first boundaries with small readable files, explicit public exports, high cohesion, low coupling, and deliberate placement of shared code and third-party services. Use when designing folder structure, splitting oversized routes or components, separating UI from validation/business logic/data access, deciding where shared code should live, or defining a module's public API.

2026-03-25
commit-conventions
ソフトウェア開発者

Follow project commit conventions when preparing commit messages and creating commits. Use when drafting, reviewing, or validating commit messages.

2026-03-06
react-engineering
ソフトウェア開発者

General React engineering skill for building and refactoring React code in this repository. Use this whenever tasks involve React components, hooks, state management, effects, rendering performance, UI composition, client/server boundaries, or React architecture decisions—even if the user does not explicitly mention "React best practices."

2026-03-01