coding-style

النجوم٤٢

التفرعات٨

آخر تحديث١٧ فبراير ٢٠٢٦ في ٢٣:٢٦

Coding standards, architecture patterns, and project conventions for the OneContext monorepo

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

robinfaraj

robinfaraj/one-context

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

مطوّرو البرمجياتمهن الحاسوب والرياضيات·SOC 15-1252

مستكشف الملفات

5 ملفات

SKILL.md

readonly

name	coding-style
description	Coding standards, architecture patterns, and project conventions for the OneContext monorepo
allowed-tools	Read, Grep, Glob
user-invocable	true
model	sonnet
context	fork

OneContext Coding Style

Apply these conventions when writing or refactoring code in this monorepo.

Reference Files

File	Scope
`coding-style.mdc`	General code quality — commenting, control flow, type derivation, business logic hygiene
`frontend.mdc`	React component patterns, composition, hooks, module organization
`backend.mdc`	Layered architecture, Hono route patterns, Zod validation, API design
`project-structure.mdc`	Monorepo layout, package descriptions, where to place new code

Key Principles

Self-documenting code — comment only to explain why, not what
Early returns — flatten logic with guard clauses; avoid deep nesting
Derive types from source — Prisma → Zod → API → frontend; avoid duplicate definitions
Follow project structure — domain-first organization; place code where it belongs
Biome for formatting — do not manually format; let the toolchain handle it
Prefer Server Components — limit use client to interactive UI concerns
UI / visual: Apply brand-guidelines for colors, typography, spacing. Copy / messaging: Apply brand-copy-guidelines for headlines, CTAs, landing copy, docs, social (tone, voice, word choice).

المزيد من هذا المستودع

نفس المستودع

test-wave

robinfaraj/one-context

Spawn a parallel agent team to create and run tests for recently implemented code. Agents analyze changes, write tests, and extend the existing test suite.

2026-02-1742

brand-copy-guidelines

robinfaraj/one-context

OneContext tone, voice, and copy rules. Use when writing or editing headlines, CTAs, landing copy, docs, in-app copy, or social content so messaging stays on-brand (direct, technical, developer-first, no AI slop).

2026-02-1642

brand-guidelines

robinfaraj/one-context

Applies OneContext's official brand colors, typography, and UI patterns. Use when building or styling UI, marketing pages, docs, or any artifact that should match the OneContext visual identity (clean, minimal, developer-first).

2026-02-1642

name	coding-style
description	Coding standards, architecture patterns, and project conventions for the OneContext monorepo
allowed-tools	Read, Grep, Glob
user-invocable	true
model	sonnet
context	fork

OneContext Coding Style

Apply these conventions when writing or refactoring code in this monorepo.

Reference Files

File	Scope
`coding-style.mdc`	General code quality — commenting, control flow, type derivation, business logic hygiene
`frontend.mdc`	React component patterns, composition, hooks, module organization
`backend.mdc`	Layered architecture, Hono route patterns, Zod validation, API design
`project-structure.mdc`	Monorepo layout, package descriptions, where to place new code

Key Principles

Self-documenting code — comment only to explain why, not what
Early returns — flatten logic with guard clauses; avoid deep nesting
Derive types from source — Prisma → Zod → API → frontend; avoid duplicate definitions
Follow project structure — domain-first organization; place code where it belongs
Biome for formatting — do not manually format; let the toolchain handle it
Prefer Server Components — limit use client to interactive UI concerns
UI / visual: Apply brand-guidelines for colors, typography, spacing. Copy / messaging: Apply brand-copy-guidelines for headlines, CTAs, landing copy, docs, social (tone, voice, word choice).