Lukk17
- 55 skills
- 0 followers
- 6 hours ago last updated
- ▌ SEO · lukk17Search visibility work across technical SEO, on-page optimisation, structured data, Core Web Vitals, keyword mapping, and internal linking. Use when you say "audit this site for SEO", "why is this page not indexed", "add schema markup to the product pages", "write titles and meta descriptions for these routes", or "map these keywords to URLs". Not for the page performance work behind Core Web Vitals, use `performance-optimization`.
- ▌ Bash · lukk17 bundleBash scripting standards covering strict mode, quoting and defensive patterns, argument parsing, exit codes, temp files, secret handling, and ShellCheck enforcement. Use when you say "write a bash script for this", "why does my script keep going after an error", "parse these flags properly", "this loop breaks on filenames with spaces", or "make ShellCheck pass". Not for PowerShell scripting on Windows, use `powershell`.
- ▌ Kicad · lukk17 bundleKiCad board design standards for board setup and custom DRC rules, IPC-2221 trace sizing, decoupling and placement, ground pours and thermal reliefs, ERC on hierarchical schematics, BOM fields, Gerber and drill export, and Git handling of project files. Use when you say "route this board", "check my DRC", "export gerbers for JLCPCB", "write a kicad_dru rule for mains clearance", or "generate a BOM with LCSC part numbers". Not for the firmware that runs on the board, use `embedded-c-arduino`.
- ▌ Unity · lukk17 bundleUnity and C# standards for allocation-free per-frame code, object pooling, Addressables load and release pairing, cached component lookups, script execution order, ScriptableObject architecture, and the Unity Test Framework. Use when you say "why does my game stutter every few seconds", "pool these bullets", "load this asset with Addressables", "cache this GetComponent call", or "write an edit mode test for this". Not for engine-agnostic C# and SOLID rules, use `coding-standards`.
- ▌ Angular · lukk17 bundleAngular application standards covering standalone components, signals and RxJS interop, dependency injection with inject(), OnPush change detection, functional guards and interceptors, typed reactive forms, and global error handling. Use when you say "build this Angular component", "replace this BehaviorSubject with a signal", "my subscription leaks", "write a functional auth guard", or "add an HTTP error interceptor". Not for React and Next.js work, use `react-patterns`.
- ▌ Ansible · lukk17 bundleAnsible standards for role structure, FQCN modules, idempotency, Vault secrets, least-privilege become, block rescue recovery, collection pinning, and the ansible-lint plus Molecule gate. Use when you say "write an Ansible role for this", "this playbook is not idempotent", "encrypt these variables with Vault", "add Molecule tests to this role", or "why does my shell task always report changed". Not for one-off host scripting, use `bash`.
- ▌ API Design · lukk17 bundleHTTP and GraphQL contract design covering resource naming, method and status-code semantics, RFC 7807 error bodies, pagination, idempotency, conditional requests, health endpoints, rate-limit headers and tiers, and versioning. Use when you say "design this endpoint", "what status code should this return", "review our API contract", "add cursor pagination to this list", or "how do we deprecate v1". Not for the service code behind the endpoint, use `backend-patterns`.
- ▌ Github Ops · lukk17Operating a GitHub repository with the gh CLI: issue triage, pull request and stale-item management, CI failure investigation, release preparation, and security alert review, read-only by default with state changes gated on approval. Use when you say "triage these issues", "which PRs are ready to merge", "CI is red, find out why", "prepare the 1.4.0 release", or "check our security alerts". Not for local branching and commits, use `git-workflow`.
- ▌ Powershell · lukk17 bundlePowerShell 7 scripting standards covering strict error handling, advanced functions and parameter validation, module layout, comment-based help, secret handling, PSScriptAnalyzer, Pester v5, and cross-platform rules. Use when you say "write a PowerShell script for this", "my script ignores when git fails", "turn this into a proper cmdlet", "add Pester tests for this module", or "make PSScriptAnalyzer clean". Not for POSIX shell scripting, use `bash`.
- ▌ E2e Testing · lukk17 bundlePlaywright browser end-to-end testing, covering suite layout, the Page Object Model, configuration, semantic locators, the canonical flaky-test policy, artifacts, and CI wiring. Use when you say "write a Playwright test for the login flow", "our e2e suite is flaky", "set up playwright.config.ts", "add e2e tests to CI", or "test the checkout journey in a browser". Not for backend capability sweeps against a live stack, use `e2e-runbooks`.
- ▌ Audio Scribe · lukk17Speech-to-text through the self-hosted AudioScribe service, covering a local faster-whisper backend, hosted API backends, and chronological speaker merging for multi-track Audacity or Craig recordings. Use when the user says "transcribe this", "what is said in this audio", "turn this recording into text", "write up this meeting", or hands you a path ending in .mp3, .wav, .m4a, .ogg, .flac, or .zip. Not for extracting text from a web page, use `ascend-web-hunter`.
- ▌ E2e Runbooks · lukk17 bundleCapability testing against a live stack, one feature per immutable spec, with behaviour-only assertions, canary fixtures, setup-cost ordering, per-run token and duration accounting, and parallel subagent orchestration. Use when you say "add an e2e test for the upload flow", "run the e2e sweep", "test that the MCP tool actually fires", "smoke test against the staging stack", or "verify this capability end to end". Not for Playwright browser UI testing, use `e2e-testing`.
- ▌ Git Workflow · lukk17 bundleGit practice for a team: branching strategy, conventional commit messages, merge versus rebase, branch naming and cleanup, pull request content, and conflict prevention. Use when you say "what should I name this branch", "write the commit message for this", "merge or rebase here", "I have a conflict in this file", or "set up our git workflow". Not for issues, pull requests and releases on the hosting platform, use `github-ops`.
- ▌ Tdd Workflow · lukk17 bundleTest-driven development discipline covering the red-green-refactor loop with an enforced RED gate, the test pyramid, mocking boundaries, test naming and structure, and a CI coverage gate of around 90 percent line coverage of real logic. Use when you say "write this feature test first", "add tests for this bug fix", "our coverage gate is failing", "what should I mock here", or "refactor this without breaking behaviour". Not for browser journeys and the flaky-test policy, use `e2e-testing`.
- ▌ Ascend Memory · lukk17Long-term semantic memory for one user through the self-hosted AscendMemory service, covering insert, semantic search, delete, and wipe against a per-user Qdrant namespace. Use when the user says "remember that…", "what did I tell you about…", "save this for later", "forget this", or when prior context about the user would change your answer. Not for fetching content from the live web, use `ascend-web-hunter`.
- ▌ Code Reviewer · lukk17Structured review of local changes or a remote pull request across correctness, maintainability, doc comments, efficiency, security, error handling and test coverage, with every finding led by a path:line reference. Use when you say "review my changes", "review PR
- ▌ Design System · lukk17Build and audit a design system: token architecture and naming, spacing rhythm, stylesheet organisation, Tailwind v4 CSS-first theming, dark mode, and visual-consistency review. Use when you say "set up design tokens", "audit this UI for consistency", "there are forty shades of grey in this codebase", "migrate us to Tailwind v4 @theme", or "review this PR for styling drift". Not for choosing the visual direction itself, use `frontend-design`.
- ▌ Code Formatter · lukk17 bundleVisual formatting and reading flow inside function bodies across Dart, Java, Python, Kotlin, TypeScript and Go: braced control-flow exits, blank lines marking phase transitions, comments above the line they describe, doc comments earning their place, one chain step per line. Use when you say "format this function", "why is this hard to read", "clean up the spacing here", or "break this method chain up". Not for naming and error handling, use `coding-standards`.
- ▌ Home Assistant · lukk17 bundleHome Assistant standards for YAML style, entity_id references, native conditions, event-driven automations, automation modes, secrets, MCP exposure limits, and backup discipline. Use when you say "write an automation for this motion sensor", "my automation retriggers and cancels itself", "move these tokens into secrets.yaml", "expose these entities to the assistant", or "why did my template condition fail silently". Not for writing a custom integration in Python, use `python-patterns`.
- ▌ React Patterns · lukk17 bundleReact patterns for component composition, custom hooks, async state, a typed API client, memoisation, code splitting, virtualisation, forms, and animation. Use when you say "build a React component", "write a custom hook", "this list re-renders on every keystroke", "lazy load this chart", or "animate this list on mount". Not for Next.js rendering, routing, and caching, use `nextjs-app-router-patterns`.
- ▌ Docker Patterns · lukk17 bundleDocker and Compose standards for multi-stage builds, pinned base images, non-root runtime users, named volumes, network isolation, build-time and runtime secrets, and the Trivy, SBOM and cosign supply-chain gate. Use when you say "write a Dockerfile for this service", "set up compose for local dev", "my container cannot reach the database", "shrink this image", or "scan and sign this image before we push". Not for Kubernetes manifests and rollout strategy, use `deployment-patterns`.
- ▌ Frontend Design · lukk17Give an interface a committed visual direction, covering composition, typography, colour, background atmosphere, and motion. Use when you say "make this page look designed", "this dashboard looks generic", "pick a visual direction for the landing page", "turn this card grid into something intentional", or "it works but it has no point of view". Not for token architecture, theming, and styling structure, use `design-system`.
- ▌ Golang Patterns · lukk17 bundleIdiomatic Go for production services and the test suite that proves them, covering zero values, interface design, error wrapping, context and cancellation, dependency injection, allocation discipline, golangci-lint v2, table-driven tests, hand-written fakes, benchmarks, and fuzzing. Use when writing a new Go package, reviewing Go code, fixing a goroutine leak, designing an interface at the consumer, setting up Go linting, converting copy-pasted tests into a table, testing an HTTP handler, or benchmarking a hot path. Not for the language-neutral SOLID, DRY, and naming floor, use `coding-standards`.
- ▌ Markdown Writer · lukk17 bundleHuman-facing markdown: README structure, an honest voice with no AI tells, Mermaid diagrams, badges, audit passes over stale docs, and translated copies. Use when you say "fix my README", "write a README for this repo", "this reads like AI wrote it", "add an architecture diagram to the docs", or "polish docs/INGESTION.md". Not for architecture decision records, which keep their own template, use `architecture-decision-records`.
- ▌ Python Patterns · lukk17 bundleIdiomatic Python for production code and the pytest suite that proves it, covering type hints, error handling, dataclasses, context managers, concurrency choice, package layout, fixtures, mocking boundaries, and the coverage gate. Use when writing a new Python module, reviewing Python code, adding type hints to a legacy file, choosing between threads, processes and asyncio, writing tests for new code, fixing a flaky pytest suite, or mocking an external API. Not for training loops, tensor code, and CUDA placement, use `pytorch-patterns`.
- ▌ Security Review · lukk17 bundleApplication security review covering secrets, input validation, injection, authentication and session handling, authorization with row-level security, XSS and CSP, CSRF, rate limiting, data exposure, and dependency risk. Use when you say "add login to this app", "review this endpoint before it ships", "we are taking payments now", "is this file upload safe", or "check this for injection". Not for container and image hardening, use `docker-patterns`.
- ▌ Backend Patterns · lukk17Language-neutral backend service design covering idempotency keys, timeouts and capped retries, the transactional outbox, cache invalidation, pagination of large reads, and graceful shutdown with liveness and readiness. Use when you say "make this endpoint safe to retry", "our webhook fired twice", "design the job queue", "this list endpoint times out on page 900", or "we drop requests during a deploy". Not for runtime-specific code, use `node-backend-patterns` or `springboot-patterns`.
- ▌ Coding Standards · lukk17 bundleThe cross-project engineering floor: SOLID, DRY, KISS, YAGNI, FIRST, intention-revealing naming, guard clauses, immutability, structured errors, layering, feature flags, and code that explains itself rather than carrying comments. Use when you say "review this for quality", "start this module properly", "refactor to our conventions", "should this have a comment", or "set up our naming rules". Not for stack-specific patterns, use a framework skill such as `springboot-patterns`.
- ▌ Jira Integration · lukk17Jira mechanics from a coding session: fetching an issue and its comments, running JQL, adding progress comments, transitioning status through the project workflow, and linking branches back to the key, through the Atlassian MCP server or the REST v3 API. Use when you say "pull up PROJ-1234", "move this ticket to In Review", "comment the PR link on the ticket", or "find my open issues this sprint". Not for how a work item should be written or closed, use `project-tracking`.
- ▌ Mongodb Patterns · lukk17 bundleMongoDB across connection pooling, query optimisation and indexing, schema design and anti-patterns, and Atlas Search, Vector Search and Hybrid Search. Use when you say "configure the connection pool", "why do I get ECONNREFUSED or pool exhaustion", "how do I optimize this query", "how do I index this", "what are the slow queries on my cluster", "design this schema", "embed vs reference", "unbounded arrays", "16MB limit", "schema validation", "time series", "polymorphic", "document versioning", "add autocomplete or fuzzy matching", "build RAG over this collection", or "combine keyword and semantic search". Not for applying a schema change safely to a live cluster, use `database-migrations`.
- ▌ Project Tracking · lukk17 bundleTracker-independent standards for planning and tracking work: kinds of work, sizing and splitting, epics as outcomes, a governed label taxonomy, statuses and how closure is recorded, testable acceptance criteria, dependency and duplicate links, bounded work in progress, and tying an item back to the code. Use when you say "write this ticket", "split this story", "are these criteria testable", "can we close this", or "triage the backlog". Not for Jira API mechanics, use `jira-integration`.
- ▌ Pytorch Patterns · lukk17 bundlePyTorch patterns for reproducible deep learning, covering device-agnostic code, seeding, nn.Module structure, training and validation loops, DataLoader throughput, checkpointing, mixed precision, torch.compile, and distributed training with DDP. Use when writing a training loop, building an nn.Module, speeding up a starved DataLoader, adding mixed precision, or scaling training across several GPUs. Not for general Python idioms and typing, use `python-patterns`.
- ▌ Soap Webservices · lukk17 bundleContract-first SOAP integration in Java, covering WSDL and XSD as the source of truth, JAXB binding files, CXF code generation, XXE prevention, WS-Security, fault taxonomy, PII-safe logging, Resilience4j retries, and MTOM. Use when you say "generate Java classes from this WSDL", "call a partner SOAP service", "add WS-Security UsernameToken", "stub a SOAP endpoint in tests", or "our SOAP client hangs". Not for REST contracts, use `api-design`.
- ▌ Ascend Web Hunter · lukk17Web search and page-content extraction through the self-hosted AscendWebSearch service, covering WAF bypass, CAPTCHA escalation to a remote browser, and cached login sessions. Use when the user says "search the web for X", "read this URL", "scrape this job listing", "this page is behind Cloudflare", or "log me in to that site so you can read it". Not for recalling facts the user told you in an earlier conversation, use `ascend-memory`.
- ▌ Keycloak Patterns · lukk17 bundleKeycloak server administration and the Keycloak.AuthServices .NET client, covering realms and clients, authentication flows and MFA, RBAC and UMA authorization, LDAP federation, hardening and clustering, plus JWT Bearer and OIDC wiring, role policies, resource protection, and the Admin and Protection API SDKs. Use when you say "set up SSO with Keycloak", "create a realm and a confidential client", "enable MFA for admins", "connect Keycloak to Active Directory", "why does my token fail audience validation", "add Keycloak auth to my .NET API", "require a realm role on this endpoint", "call the Keycloak Admin API from C#", or "protect this resource with UMA". Not for Spring Security resource-server configuration, use `springboot-patterns`.
- ▌ Postgres Patterns · lukk17PostgreSQL working reference for index selection, data types, row-level security, cursor pagination, queue processing, anti-pattern detection queries, server configuration, replica routing, alert thresholds, backups, and erasure. Use when you say "which index does this query need", "why is this query slow", "write an RLS policy for this table", "should this be numeric or float", or "find our unindexed foreign keys". Not for applying a schema change safely, use `database-migrations`.
- ▌ Web Accessibility · lukk17Accessibility for web interfaces to WCAG 2.2 AA, covering semantic HTML, keyboard operability, focus management, correct ARIA, colour contrast, accessible forms and images, target size, and reduced motion. Use when you say "is this component accessible", "audit this page against WCAG", "trap focus in this modal", "the screen reader skips my error message", or "check these colours for contrast". Not for the visual direction a palette expresses, use `frontend-design`.
- ▌ Embedded C Arduino · lukk17 bundleEmbedded C and Arduino standards for heap-free memory discipline, bounded loops and watchdogs, non-blocking millis state machines, ISR flag-and-return, fixed-width integer types, MISRA C 2012 style, a hardware abstraction layer, and host-side unit tests. Use when you say "replace this delay with a state machine", "write the ISR for this encoder", "my sketch runs out of SRAM", "unit test this firmware on the host", or "add a watchdog". Not for the PCB the firmware runs on, use `kicad`.
- ▌ G Code 3d Printing · lukk17 bundleG-code and 3D printing standards for thermal and motion safety, absolute positioning, Klipper macros over raw G-code, start and end sequences with bed mesh and purge line, filament calibration, and slicer profile version control. Use when you say "write start G-code for my printer", "my nozzle drags through the print", "set up a START_PRINT macro", "calibrate pressure advance", or "version my slicer profiles". Not for the PCB inside the printed part, use `kicad`.
- ▌ Review Duplication · lukk17Investigate a change for duplicated logic, reinvented utilities, and missed reuse of the project's existing helpers, patterns and installed libraries, then report what should have been reused and how. Use when you say "check this PR for duplication", "did we already have a function for this", "is this reinventing something", "why is there a second date formatter", or "review this for reuse before I approve it". Not for a full multi-pillar review pass, use `code-reviewer`.
- ▌ Agentic Engineering · lukk17Running engineering work where agents write most of the code and a human holds the quality bar: eval-first execution, agent-sized decomposition, capability-tier routing, approval and escalation, context budgeting, and multi-agent coordination. Use when you say "plan this work for agents", "which tier should run this", "split this into agent-sized units", or "set up evals before we start". Not for building the regression suite itself, use `ai-regression-testing`.
- ▌ Database Migrations · lukk17 bundleSafe, reversible schema and data migrations for production databases, covering lock-free column and index changes, expand-contract renames, batched backfills, explicit constraint names, rollback strategy, and the review gates a migration must pass. Use when you say "add a column to this table", "create this index without downtime", "rename a column safely", "backfill ten million rows", or "how do we roll this migration back". Not for index choice and query tuning, use `postgres-patterns`.
- ▌ Deployment Patterns · lukk17 bundleDeployment and CI/CD standards covering rolling, blue-green and canary rollouts, an approval gate before production, GitHub Actions with OIDC and least-privilege permissions, health probes, config validation, rollback, and Kubernetes defaults. Use when you say "set up a CI/CD pipeline", "add a canary rollout", "why did merging to main deploy to prod", "add readiness and liveness probes", or "how do we roll this back". Not for writing the Dockerfile itself, use `docker-patterns`.
- ▌ Springboot Patterns · lukk17 bundleSpring Boot services end to end on blocking Spring MVC: controller, service and repository layering, RFC 7807 errors, RestClient wrapped in Resilience4j, caching and events, Spring Security 6 authentication, authorization, headers and rate limiting, JPA mapping, N+1 and HikariCP, JUnit 5 and Testcontainers tests, and the pre-merge build, scan and coverage pipeline. Use when you say "structure this Spring Boot API", "add JWT auth to this endpoint", "lock this down to admins", "why does this query run two hundred times", "write a @WebMvcTest for this controller", "rate limit this endpoint", or "verify this before I open the PR". Not for Java language style, naming, records and Optional usage, use `java-coding-standards`.
- ▌ Automation Inventory · lukk17Evidence-first inventory of every live automation: scheduled jobs, hooks, CI workflows, connectors, MCP servers and wrapper scripts, each classified as configured, authenticated, verified, stale or missing, and each claim backed by a command and its output. Use when you say "what automations do I have", "what is actually running", "which of these jobs is broken", or "audit our tooling before we fix anything". Not for operating one CI system, use `github-ops`.
- ▌ AI Regression Testing · lukk17 bundleRegression testing for the blind spots of AI-assisted development: bug-driven test selection, response-contract assertions, sandbox and production path parity, and a mechanical check step before any AI review. Use when you say "an agent changed my API routes", "write a regression test for this bug", "the same bug keeps coming back", "test this without a database", or "the sandbox path drifted from production". Not for the red-green-refactor loop and the coverage gate, use `tdd-workflow`.
- ▌ Dart Flutter Patterns · lukk17 bundleDart 3 and Flutter patterns across architecture, layout, routing, forms, networking, persistence, concurrency, animation, accessibility, localization, native interop, app size, and testing. Use when you say "build a Flutter screen", "why does my Column overflow", "set up GoRouter with an auth guard", "parse this JSON without jank", or "write a widget test for this form". Not for language-neutral SOLID, naming, and error-handling rules, use `coding-standards`.
- ▌ Java Coding Standards · lukk17 bundleJava language standards for Spring Boot services: naming, Lombok and constructor injection, immutability and records, Optional, streams, exceptions, generics, null safety, SLF4J logging, and Javadoc discipline. Use when you say "review this Java class", "should this be a record", "is this Optional usage correct", "rename these methods properly", or "set up Checkstyle and SpotBugs". Not for Spring Boot wiring and REST structure, use `springboot-patterns`.
- ▌ Node Backend Patterns · lukk17 bundleNode.js server-side patterns for Express and Next.js route handlers, covering repository and service layering, query batching, RFC 7807 errors, typed config, pino logging, and graceful shutdown. Use when you say "structure my Express API", "fix the N+1 in this route", "cache this Prisma query", "rate limit this endpoint", or "my Node app never exits on SIGTERM". Not for language-neutral backend design, use `backend-patterns`.
- ▌ Hexagonal Architecture · lukk17 bundlePorts and adapters design covering domain and use-case boundaries, inbound and outbound ports, dependency inversion, adapters, the composition root, and per-boundary testing in TypeScript, Java, Kotlin and Go. Use when you say "restructure this around ports and adapters", "my domain imports the ORM", "test this use case without a database", or "swap this payment provider". Not for HTTP contract design, use `api-design`.
- ▌ Performance Optimization · lukk17Measure-first performance work for application code and data access, covering profiling, N+1 queries, fetch and index discipline, caching with an invalidation rule, streaming, and concurrent IO. Use when you say "this endpoint is slow", "the page takes four seconds to load", "profile this before I change anything", "did my change regress latency", or "this query runs inside a loop". Not for schema and index design on Postgres itself, use `postgres-patterns`.
- ▌ Observability And Logging · lukk17 bundleStructured logging and production observability for services, covering log levels, correlation IDs, health checks, metrics, tracing, SLOs, resilient outbound calls, graceful shutdown, and the startup readiness banner. Use when you say "add logging to this service", "my logs have no trace id", "add a readiness probe", "put a timeout and retry on this client", or "print a startup banner when the app is up". Not for CI/CD pipelines and release gating, use `deployment-patterns`.
- ▌ Nextjs App Router Patterns · lukk17 bundleNext.js App Router architecture covering Server and Client Components, caching, streaming, Server Actions, route handlers, metadata, images, and Turbopack dev tuning. Use when you say "build a Next.js page", "server or client component", "revalidate this fetch", "add a server action", "parallel routes for a dashboard", or "next dev is slow". Not for framework-agnostic React state, hooks, and animation, use `react-patterns`.
- ▌ Build Dependency Management · lukk17Build files and dependency versions: one central version catalog, bill-of-materials imports, shared build logic, locked reproducible installs, and deliberate dependency admission. Use when you say "add this dependency", "set up the Gradle build", "centralise our versions", "import the Spring Boot BOM", or "why do two modules use different versions of the same library". Not for Java language style, use `java-coding-standards`.
- ▌ Architecture Decision Records · lukk17Capturing an architectural decision as a numbered ADR with context, the decision, rejected alternatives and honest consequences, plus the directory layout, the index, the status lifecycle and how to detect a decision moment in a working session. Use when you say "record this decision", "ADR this", "we decided Postgres over Mongo", "why did we choose this framework", or "write up the trade-off we just settled". Not for the implementation plan that follows the decision, use `project-tracking`.