Claude Skills by EdytaKucharska

Reviews a proposed or existing software architecture for a product, feature, or system. Use this skill PROACTIVELY whenever the user describes how their product is structured, proposes a new architecture, mentions splitting or merging services, brings up data model decisions, discusses scaling, or asks any structural "how should we build this" question — even if they don't explicitly ask for an architecture review. Common trigger phrases include "should we use microservices", "should we split...

The whole-project readiness review of an existing codebase. Invoke when the user EXPLICITLY runs /keel:deep-review, or asks for a comprehensive/full/deep review of their whole project — "is my app production-ready?", "review the whole project before I launch / before I start charging", "give my codebase a health check", "what will break when I get users?", "audit my whole project". Mentioning launching, charging, or getting paid does NOT make this an enterprise/compliance question — with no s...

The enterprise-sales security gauntlet. Invoke PROACTIVELY when a SPECIFIC customer, prospect, or deal is applying security or compliance scrutiny — a security questionnaire received (or expected from a named prospect), a customer's procurement/InfoSec/legal review, being asked for SOC 2 / ISO 27001 / a DPA / a pen-test report, "our first big customer wants...", "do we need SOC 2?", or deliberate preparation for moving upmarket. Requires a customer-shaped counterparty in the conversation: a g...

Invoke PROACTIVELY (do NOT judge the number directly, and NEVER produce a counter-estimate) whenever the user reports an engineering estimate, quote, or timeline someone gave them — "my engineer says 6 weeks, is that real?", "the agency/freelancer quoted 3 months", "is N weeks reasonable for [feature]?", "my dev says we can't ship without rebuilding X first" — or is deciding whether to approve, push back on, or defer quoted work. Fires on ANY reported estimate from an employee, agency, contra...

Invoke PROACTIVELY (do NOT answer the implementation question directly, and do NOT re-brainstorm the feature) whenever a user wants to add a feature or capability to a product that already exists — "we want to add X", "how should we build [feature]?", "users are asking for X", "what's the right approach for [capability]?", a shared PRD/spec/ticket, or the post-brainstorm handoff "now how should we build this?". This skill owns the technical-approach moment: when the feature's intent is alread...

Invoke PROACTIVELY (do NOT answer the build question directly) whenever a user wants to turn a product idea into a first build and no code exists yet — "I want to build an app/SaaS/tool that does X", "where do I start", "what would it take to build X", "what stack for a new X", or the post-brainstorm handoff "ok, now how do I actually build this?". This skill owns the HOW-do-I-build-it moment for pre-product ideas; brainstorming and idea-exploration skills own the earlier WHAT-should-this-be ...

Prepares a founder for investor technical due diligence — the moment a term sheet or serious interest turns into "our technical advisor wants to look at the codebase / meet your team / see the architecture." Use this skill PROACTIVELY when the user mentions upcoming technical due diligence, an investor asking technical questions, "we're raising and they want to review our tech", "a VC's engineer wants a call about our architecture", "what will investors look at in the codebase", "preparing a ...

Evaluates a proposed technology choice (library, framework, ML model, infrastructure component, third-party service, or any new dependency) before it gets adopted into a project. Use this skill PROACTIVELY whenever the user mentions adopting, using, integrating, switching to, or building on top of a specific named technology — even if they don't explicitly ask for an evaluation. Common trigger phrases include "I'm thinking of using X", "should I use X", "let's go with X", "I'll add X", "we ca...

Recommends how to build a proposed feature — the simplest viable design, what to defer, what to prove first, build vs. buy, and what the feature implies for the rest of the system. Use this skill PROACTIVELY whenever the user describes a feature they want to build, asks "how should we build X", proposes adding functionality, drafts a feature spec, or mentions wanting to ship something new — even if they don't explicitly ask for a design memo. Common trigger phrases include "we want to add X",...

Assesses cloud and infrastructure costs — current spend, projected spend, cost-per-unit (request/user/feature), top line items driving the bill, optimisation opportunities with ROI, and lock-in risks. Use this skill PROACTIVELY whenever the user mentions infrastructure costs, cloud bills, vendor pricing, scaling cost, "our bill is too high", "we're burning cash on infra", "is this expensive at scale", or shares a bill, an architecture with cost implications, or a pricing page. Common trigger ...

Audits a product's technical hygiene — backups, secrets, observability, deployment, basic security, testing on critical paths, and the operability of any AI-generated code. Produces a ranked list of "needed yesterday" items (non-negotiable) vs. "you don't need this yet" items (defer with a trigger). Use this skill PROACTIVELY when the user asks "is my system production-ready", "audit my project", "what should I clean up before [investors / customers / scaling]"; mentions shipping with AI tool...