post-edit-conventions
Monorepo coding conventions to follow when writing or editing code in this repository
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- post-edit-conventions
- description
- Monorepo coding conventions to follow when writing or editing code in this repository
- user-invocable
- false
03 SKILL.md 正文
Coding Conventions
Always follow these conventions when writing or editing code in this monorepo:
Formatting
- Tabs for indentation (never spaces)
- Biome handles formatting — don't manually adjust style
File Extensions
- No
.jsfiles — use.mjsor.cjsfor JavaScript - TypeScript files use
.ts(ESM is default via"type": "module") - This is enforced by the
NoJsFileExtensionsrepopo policy
Imports
- No barrel re-exports — import directly from the source module, not through index files
- Use
patheinstead ofnode:pathfor cross-platform path handling - Use
fs/promises(async) instead offssync methods (readFilenotreadFileSync) - Use explicit file extensions in imports where required
Dependencies
- Internal workspace deps use
workspace:^protocol - Never add runtime dependencies to
@tylerbu/fundamentals(zero-dep package) - Use
pnpmexclusively (never npm or yarn)
TypeScript
- Use proper types — avoid
any - Prefer
satisfiesoverasfor type assertions - Don't add lint-disable comments to work around type issues
- All packages extend base tsconfig from
config/tsconfig.strict.json
Package Structure
- Output directory is
esm/(notdist/orlib/) - Source in
src/, tests intest/ - Every package needs
"type": "module"in package.json - Package.json keys must be sorted (enforced by repopo)
Testing
- Use Vitest (not Jest)
- Test files:
test/**/*.test.ts - Merge base config:
import defaultConfig from "../../config/vitest.config"
04 同仓库更多 Skills
unslop
Cut AI tells from any writing.
storytelling
Make sure all prose sentences contribute to a coherent narrative, forming a small story rather than a series of disconnected statements.
stop-slop
Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.
prose-banlist
A skill that bans certain phrases from being used in prose writing.
ponytail
Lazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.
ponytail-review
Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review.