All authors
Claude Skills by Amey-Thakur
github.com/Amey-Thakur1,001 skills16 installs1,473 views
- Platform As ProductRun an internal platform with users, feedback, and adoption metrics rather than as a mandated standard. Use when platform adoption is poor or teams complain about the tools they are required to use.Votes: 0GitHub stars: 7
- Policy As CodeExpress organisational rules as automated checks in the pipeline rather than as documents people are meant to follow. Use when standards exist on paper and are inconsistently applied.Votes: 0GitHub stars: 7
- Self Service InfrastructureLet teams provision what they need within guardrails, without waiting for an infrastructure team to act. Use when provisioning requests queue and infrastructure work is reactive.Votes: 0GitHub stars: 7
- Service CatalogMaintain an inventory of services with owners, dependencies, and operational metadata so questions about who owns what are answerable. Use when nobody can say who owns a service or what depends on it.Votes: 0GitHub stars: 7
- Ab Test DesignDesign product experiments with real hypotheses, honest sample-size math, guardrails, and peeking discipline. Use when validating a change by experiment or reviewing a test before believing its result.Votes: 0GitHub stars: 7
- Customer InterviewsRun user interviews that surface past behavior instead of polite predictions, recruited and synthesized honestly. Use when gathering qualitative evidence for product decisions.Votes: 0GitHub stars: 7
- Feature SunsettingRemove features with usage evidence, migration paths, and staged communication that preserves trust. Use when retiring product surface or making the case that something should die.Votes: 0GitHub stars: 7
- Mvp ScopingScope minimum viable products around the riskiest assumption, cut to learn fast, and hold an explicit quality floor. Use when defining a first version or rescuing an MVP that grew into a v3.Votes: 0GitHub stars: 7
- Prioritization FrameworksPrioritize with RICE-class scoring applied honestly, cost of delay, and refusals that carry reasons. Use when ordering a roadmap or defending priority calls under stakeholder pressure.Votes: 0GitHub stars: 7
- Product DiscoveryValidate problems before building solutions using evidence standards and opportunity mapping. Use when deciding what to build next or challenging a solution that arrived before its problem.Votes: 0GitHub stars: 7
- Product LaunchLaunch features through tiered rollouts, a readiness checklist, coordinated comms, and a post-launch review. Use when shipping something users will notice or coordinating a cross-team release moment.Votes: 0GitHub stars: 7
- Product MetricsChoose a north star with input metrics you can move, guardrails you must not break, and defenses against vanity. Use when defining product measurement or auditing a dashboard full of numbers nobody acts on.Votes: 0GitHub stars: 7
- Roadmap CommunicationCommunicate roadmaps with now/next/later horizons, honest commitment levels, and audience-shaped views. Use when publishing product direction or managing the fallout of roadmap changes.Votes: 0GitHub stars: 7
- User Story WritingWrite user stories around outcomes with testable acceptance criteria, sliced thin enough to ship in days. Use when turning product intent into buildable work or fixing a backlog of vague tickets.Votes: 0GitHub stars: 7
- Cross Team CoordinationKeep work moving across team boundaries with explicit interfaces, owners, and shared checkpoints. Use when a project spans teams and progress stalls at handoffs.Votes: 0GitHub stars: 7
- Milestone PlanningBreak a project into milestones that each prove something, so progress is verifiable rather than asserted. Use when a project is long enough that the end is not visible from the start.Votes: 0GitHub stars: 7
- Project ClosureEnd a project deliberately, with handover, documentation, and a decision about what happens to what was built. Use when a project reaches its goal or is being stopped.Votes: 0GitHub stars: 7
- Project KickoffStart a project with shared understanding of goal, roles, and working agreements, so early ambiguity does not become late rework. Use at the start of any multi-person project.Votes: 0GitHub stars: 7
- Project RetrospectiveReview a completed project to extract what should change next time, focusing on systems rather than individuals. Use at the end of a project or a significant phase.Votes: 0GitHub stars: 7
- Project Risk ManagementIdentify what could derail a project, decide responses in advance, and track them rather than reacting when they happen. Use at project start and at every major checkpoint.Votes: 0GitHub stars: 7
- Project ScopingDefine what a project includes, excludes, and depends on before work starts, so scope disagreements surface early. Use when starting a project or when a project keeps growing.Votes: 0GitHub stars: 7
- Project Status ReportingReport progress in a form that surfaces problems early and lets a reader act, rather than reassuring. Use when reporting to sponsors or across teams.Votes: 0GitHub stars: 7
- Resource PlanningMatch people and capacity to project needs over time, accounting for partial allocation, ramp-up, and the cost of splitting attention. Use when planning who works on what across projects.Votes: 0GitHub stars: 7
- Schedule And Critical PathSequence work by dependency to find which tasks actually determine the finish date, and manage those. Use when a project has many parallel workstreams and an immovable date.Votes: 0GitHub stars: 7
- Scope Change ControlHandle new requests mid-project by making the trade-off visible rather than absorbing them silently. Use when a project is accumulating additions and the date is not moving.Votes: 0GitHub stars: 7
- Chain Of Thought PromptingAsk a model to reason before answering when the task needs intermediate steps, and know when it costs more than it gives. Use for multi-step reasoning, and avoid it for simple retrieval or formatting.Votes: 0GitHub stars: 7
- Context PlacementDecide where in a prompt to put documents, history, and instructions, given that models attend unevenly across a long context. Use when prompts are long and the model ignores material in the middle.Votes: 0GitHub stars: 7
- Few Shot ExamplesTeach a task by showing worked examples, chosen and ordered so the model generalises the pattern rather than copying the specifics. Use when instructions alone produce inconsistent format or judgement.Votes: 0GitHub stars: 7
- Negative InstructionsTell a model what not to do in a way that works, by converting prohibitions into positive alternatives wherever possible. Use when a prompt lists things to avoid and the model keeps doing them.Votes: 0GitHub stars: 7
- Output Format ControlGet output in exactly the structure downstream code expects, using schemas, examples, and validation rather than hope. Use when a model's output is parsed by a program rather than read by a person.Votes: 0GitHub stars: 7
- Prompt ConstraintsExpress limits on length, scope, style, and behaviour so they are followed rather than politely ignored. Use when a model consistently exceeds bounds or drifts outside the task.Votes: 0GitHub stars: 7
- Prompt IterationImprove a prompt through controlled changes measured against a fixed set of cases, rather than by rewriting until an example looks good. Use when a prompt underperforms and each edit is a guess.Votes: 0GitHub stars: 7
- Prompt StructureOrder a prompt so the model knows its task, its material, and its output before it starts generating. Use when writing any non-trivial prompt or fixing one that produces the wrong shape of answer.Votes: 0GitHub stars: 7
- Prompt TestingTest prompts like code, with a case set, pass criteria, and regression runs on every change including model upgrades. Use when a prompt is in production and its behaviour matters.Votes: 0GitHub stars: 7
- Prompt VersioningManage prompts as versioned artefacts with review, rollback, and a record of what changed and why. Use when prompts affect production behaviour and more than one person edits them.Votes: 0GitHub stars: 7
- Role And Persona PromptingAssign a role to shape expertise, register, and priorities, without pretending it grants knowledge the model lacks. Use when output should read as written by a particular kind of expert for a particular audience.Votes: 0GitHub stars: 7
- System Prompt DesignWrite the durable instructions that shape every turn, covering role, boundaries, and defaults without micromanaging each response. Use when configuring an assistant or agent that will handle many different requests.Votes: 0GitHub stars: 7
- Pytest MasteryStructure pytest suites with fixtures, parametrize, and markers so tests stay fast, isolated, and readable. Use when writing Python tests or untangling a slow, fixture-heavy suite.Votes: 0GitHub stars: 7
- Python AsyncioDecide whether asyncio pays off, keep the event loop unblocked, and structure concurrency with TaskGroup and disciplined cancellation. Use when writing async Python or diagnosing a hung, slow, or silently-failing event loop.Votes: 0GitHub stars: 7
- Python Cli ToolsBuild Python command-line tools with correct exit codes, stream discipline, and a distributable entry point. Use when writing or packaging a CLI in Python.Votes: 0GitHub stars: 7
- Python ConcurrencyChoose threads, processes, or asyncio from workload shape, and use concurrent.futures without deadlocks. Use when parallelizing Python work or debugging concurrency that is slower than sequential.Votes: 0GitHub stars: 7
- Python DataclassesChoose between dataclass, NamedTuple, and pydantic, and configure frozen, slots, and validation correctly. Use when modeling structured data in Python or reviewing class boilerplate.Votes: 0GitHub stars: 7
- Python DecoratorsWrite decorators that preserve signatures and compose cleanly, including parameterized and class-applied forms. Use when adding cross-cutting behavior to Python functions or fixing decorator-related introspection breakage.Votes: 0GitHub stars: 7
- Python EnvironmentsPick an environment manager, pin dependencies with a lockfile, and produce reproducible installs that never touch system Python. Use when setting up a project's dependencies, fixing "works on my machine", or hardening CI installs.Votes: 0GitHub stars: 7
- Python Error HandlingDesign exception hierarchies, catch narrowly, and preserve error context so failures stay diagnosable. Use when structuring errors in a Python library or application, or cleaning up broad except blocks.Votes: 0GitHub stars: 7
- Python GeneratorsBuild lazy pipelines with generators and itertools, trading materialized lists for constant memory, and know when eager evaluation is the right call. Use when processing streams, large or infinite sequences, or composing data transformations.Votes: 0GitHub stars: 7
- Python PackagingPackage a Python project with a single pyproject.toml, a src layout, and a clean build/publish path to PyPI including entry points. Use when turning a script or library into an installable, distributable package.Votes: 0GitHub stars: 7
- Python PerformanceProfile first, then remove Python-level overhead through vectorization, better algorithms, or a compiled extension. Use when Python code is too slow and you must decide where and how to optimize.Votes: 0GitHub stars: 7
- Python Project StructureOrganize Python packages so imports stay clean, cycles cannot form, and the layout scales with the codebase. Use when starting a Python project or untangling circular imports and grab-bag modules.Votes: 0GitHub stars: 7
- Python TypingAdd type hints where they catch real errors and document contracts, choosing Protocol, generics, or TypedDict deliberately and setting a checker strictness you can actually hold. Use when introducing or tightening types on a Python codebase.Votes: 0GitHub stars: 7