victorzhuk/skills

z-no-ai-style-code

Write like a senior maintainer of this project, not a tutorial — natural short names, concise error context, structure matching the surrounding code's idiom.

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/victorzhuk/skills --skill z-no-ai-style-code

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

No AI-style code

Match the file you're editing. New code should read like the maintainer who owns this file wrote it on an ordinary day — not like a textbook example generated in isolation.

Core rules

  • Short, natural names over descriptive-but-bloated ones: cfg, repo, srv, pool — not applicationConfiguration, userRepositoryInstance, httpServerInstance, databaseConnectionPool.
  • Error context is a phrase, not a sentence: "create user: %w", not "failed to create user in the database: %w".
  • Don't split a type into an Interface + Impl pair for one concrete implementation — see [[z-no-over-engineering]].
  • Before writing, read a neighboring file in the same package and match its naming density, abstraction level, and idiom. A diff that looks more "polished" than its surroundings is a signal, not a compliment.
  • Prefer the shape the codebase already uses over a textbook-correct alternative it doesn't use — consistency with the file beats abstract correctness.

Examples

AI-style — avoid:

go
applicationConfiguration := config.Load()
userRepositoryInstance := userRepo.New(pool)
httpServerInstance := NewServer(cfg)

if err != nil {
    return fmt.Errorf("failed to create user in database: %w", err)
}

type UserServiceInterface interface { ... }
type UserServiceImpl struct { ... }

Natural — match this:

go
cfg := config.Load()
repo := userRepo.New(pool)
srv := NewServer(cfg)

if err != nil {
    return fmt.Errorf("create user: %w", err)
}

type UserService struct { ... }

Do not

  • Name a variable after its type (userRepositoryInstance UserRepository) — the type is already visible at the declaration.
  • Wrap an error with a phrase that repeats the callee's own wrap ("get user: get user by id: %w").
  • Reach for an interface, factory, or builder because it's "more testable" with no second concrete case in sight.
  • Write a docstring-style block comment above a function whose name already says what it does.

Verify

Read one existing file in the same package before finishing the diff; the new code should be indistinguishable in tone from what's already there.

dallo stesso repository

Altri Skills

Tutti gli Skills
victorzhuk
Community

z-accessibility

Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".

installazioni
1
GitHub Stars
0
Aggiornato
22 ott
victorzhuk
Community

z-algo-core

DS/algorithm selection judgment for production code, not competitive tricks — hash map for membership/dedup, slice+sort beats a tree until proven, heap for top-k, two-pointer/sliding-window for scans, BFS/DFS/topo-sort for dependency shapes. Triggers on Big-O, hash map vs tree. Does not cover profiling/tuning; see [[z-go-performance]].

installazioni
1
GitHub Stars
0
Aggiornato
22 ott
victorzhuk
Community

z-bdd

BDD acceptance contracts for humans and agents across UI, API, and CLI products. Use for Gherkin, Given-When-Then, E2E acceptance, or scenario evidence. Define repeatable scenarios with explicit assertions and required outcomes. Test selection belongs to [[z-testing-strategy]]. Go harness wiring belongs to [[z-go-bdd]].

installazioni
1
GitHub Stars
0
Aggiornato
22 ott
victorzhuk
Community

z-codegraph

Use an existing CodeGraph integration for call graphs, impact analysis, affected tests, or route discovery. Discover installed tools and index freshness; follow host LSP precedence and verify current source. Do not initialize indexes without user authorization.

installazioni
1
GitHub Stars
0
Aggiornato
22 ott