standards
/standards
Zamienia konwencje projektu w standardy sprawdzane maszynowo: nazewnictwo, brak sekretów w kodzie i system projektowy.
- Autor
- ciro-maciel ↗
- Repozytorium
- ccm-stack ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 10.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 10.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Zamienia konwencje projektu w standardy sprawdzane maszynowo: nazewnictwo, brak sekretów w kodzie i system projektowy.
Wyzwalacze z opisu
Oryginalny opis (EN)
Give a project standards a machine keeps - measure what the code already does, propose ccm.standards.json (naming, API keys, the Zen design system), and from then on every write and commit is checked, refusing only what a change adds. Use when a project has no conventions, when asked to "set our standards", "enforce naming", "stop secrets in code", or after a review keeps finding the same deviation.
Jak działa
- 1. Measure before proposing
- 2. Propose, then let the team decide
- 3. Prove it refuses
- 4. Know where the project stands
- The rules of the packs
- Exceptions
- Secrets already in the history
Podgląd SKILL.md
--- name: standards description: Give a project standards a machine keeps - measure what the code already does, propose ccm.standards.json (naming, API keys, the Zen design system), and from then on every write and commit is checked, refusing only what a change adds. Use when a project has no conventions, when asked to "set our standards", "enforce naming", "stop secrets in code", or after a review keeps finding the same deviation. --- # Standards a machine keeps A standard written in a document is followed until someone forgets it. A standard in `ccm.standards.json` is checked the moment an agent writes a file, again at every commit (whoever commits), and on demand for the whole tree. Only what a change adds is refused, so adopting a standard today never blocks work on the code written before it. ## 1. Measure before proposing ``` ccm standards init ``` It reads the code and says, pack by pack, how much of the project already follows each standard. It writes nothing. Show the person the numbers in plain words: "9 in 10 files already name booleans as questions", "two secrets are in the code today". ## 2. Propose, then let the team decide The file is the team's, not yours. The proposal follows what most of the project already does: | Pack | Proposed on when | |---|---| | `api-keys` | Always: a secret in code or in a commit is a leak in any project | | `naming` | 80% or more of the files already follow it | | `zen` | The project uses `@ciromaciel/components-kit` | A pack the project mostly does not follow is proposed off: turning it on is a decision for the team, never yours. When they agree, write it: ``` ccm standards init --write ``` Commit `ccm.standards.json`, so every person, agent and editor reads the same standards. ## 3. Prove it refuses Write one deviation on purpose (a `userID`, a key in a source file) and show the refusal and its fix. A standard that has never refused anything has not been tested. ## 4. Know where the project stands ``` ccm standards report ``` Every pack, active or not, with the files that deviate most. Use it to plan cleanups; never fix the whole tree in an unrelated change. ## The rules of the packs - **naming**: `Id`, never `ID`; a boolean is an affirmative question (`isOpen`, `hasAccess`, `canEdit`, `shouldRetry`); a new script file is kebab-case. Strings and comments are not checked. - **api-keys**: no secret in code; the env file is the right place and is never committed. Public keys pass. - **zen**: radius 0, no shadows, the gray ramp only (`red.6` for errors), Montserrat 500/700/800/900, Tabler icons. Screens and styles only: an e-mail template keeps its hex colors. ## Exceptions A line that is a real exception says so where the next person reads it: `// ccm: allow <the reason>`. A folder that is out of scope goes in `ignore` in the file. Never turn a pack off to get one change through. ## Secrets already in the history Untracking a file does not remove what was pushed. Say so, and ask the person to rotate every key the report found: that is theirs to do, in each service.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · ciro-maciel/ccm-stack | 100 | MIT |
| NathanColosimo/skills | 100 | MIT |
| itamarzand88/cli-anything-web | 100 | MIT |
| prashantxo/codeforge | 100 | MIT |
| danielchukuma-dev/cougr | 95 | MIT |
| stellar/stellar-dev-skill | 90 | Apache-2.0 |
| rylsherdamz-rgb/stellar-forge | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki b9b62c8e9ea2 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100api-standards
Egzekwuje standardy projektowania i nadzoru nad API REST i GraphQL: projekt API, przegląd standardów i governance. - 100api-standards
Stosuje niezależne od firmy standardy projektowania API HTTP: kształt REST, wersjonowanie, błędy i nazewnictwo, przy projektowaniu lub przeglądzie API. - 100local-awesome-code-standards-c28c96db
Podaje uniwersalne standardy kodu: nazewnictwo, strukturę, obsługę błędów i warstwy backendu, uzupełniając konwencje projektu. - 100coding-standards
Opisuje wspólne konwencje kodowania: nazewnictwo, czytelność, niezmienność i jakość przeglądu dla projektów bez zasad frameworka. - 100write-code
Opisuje styl i konwencje pisania kodu w Rust dla Syncpack: wzorce funkcyjne, importy, nazewnictwo i standardy jakości. - 95coding-standards
Podaje bazowe konwencje kodowania dla wielu projektów: nazewnictwo, czytelność, niemutowalność i przegląd jakości kodu, gdy nie ma skilla właściwego dla danego frameworka.