Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

willey-labs

@willey-labs source repo

2 published skills

  1. ▌
    Coding Standards · willey-labs bundle
    Coding standards for writing, editing, and reviewing code. Routes to language/framework-specific rules (Next.js, NestJS, Laravel, vanilla JS/TS, NativeScript, React Native/Expo, C#/.NET, Node Express/Fastify, Cocos Creator, Vue/Nuxt, Spring Boot, Django, FastAPI, Flask, Go HTTP) PLUS universal clean-code rules (functions, naming, objects/data, formatting, error handling, SOLID/KISS/DRY, universal structural rules) that apply to every language. Consult before any code change. Use when the user says "write a component", "add an endpoint", "refactor this", "review this diff/PR", or "is this clean?". Make sure to consult this skill for ANY code authoring or review task, even when the user does not explicitly ask for "standards" — every write/edit/review must comply.
    0
    installs
  2. ▌
    Writing Standards · willey-labs bundle
    Standards for writing, editing, and reviewing DOCUMENTS — READMEs, specs, rules, skills, design docs, guides, and any prose deliverable produced from a source (existing code, or a prior discussion). Two rule sets apply on every document task: (1) source-to-deliverable — code→doc describes what the system DOES with no code or code-identifiers; discussion→rule states the general principle, not the specific example just discussed; (2) anti-slop — cut hedging, hype words, throat-clearing, cheerleading, reflexive formatting, and padding. Use when the user says "write a document", "document this code", "write up what this does", "turn this into a rule/skill", "make a doc from our discussion", "review this doc", or "is this slop?". Consult before authoring or reviewing ANY document, even when the user does not say "standards" — every document write/edit/review must comply. The companion to coding-standards: that one governs code, this one governs documents.
    0
    installs