All authors
Claude Skills by Amey-Thakur
github.com/Amey-Thakur1,001 skills16 installs1,473 views
- Email EtiquetteFollow email conventions that keep you professional and considerate: CC/BCC, reply-all, response times, and threading. Use when unsure of the norms, or to avoid the mistakes that annoy colleagues and burn goodwill.Votes: 0GitHub stars: 7
- Email Follow UpsFollow up on unanswered emails effectively: the right timing, adding value, and knowing when to stop. Use when an email went unanswered and you need a reply without nagging or damaging the relationship.Votes: 0GitHub stars: 7
- Email StructureStructure an email so a skimming reader gets the point, the context, and the ask in the right order. Use when an email has more than a line or two and the layout decides whether it is understood.Votes: 0GitHub stars: 7
- Email Subject LinesWrite subject lines that get emails opened and found later: specific, honest, and action-signaling. Use when the subject line decides whether your email is opened, prioritized, or buried.Votes: 0GitHub stars: 7
- Email ToneGet the tone of an email right: warm, professional, and matched to the reader and situation, without the coldness email invites. Use when an email's wording could land wrong, or when the relationship matters as much as the message.Votes: 0GitHub stars: 7
- Inbox ManagementManage an email inbox so it is a task list you control, not a source of stress: triage, process, and protect focus. Use when email volume is overwhelming or the inbox has become an anxiety pile.Votes: 0GitHub stars: 7
- Embedded DebuggingDebug firmware with JTAG/SWD workflows, console-free logging, and hard-fault analysis that names the faulting line. Use when a device crashes, hangs, or misbehaves only in the field.Votes: 0GitHub stars: 7
- Embedded Memory ConstraintsFit firmware into kilobytes with static allocation, measured stack sizing, and linker-map budgeting. Use when developing on microcontrollers or debugging overflows and fragmentation on-device.Votes: 0GitHub stars: 7
- Firmware Ota UpdatesShip over-the-air firmware with A/B slots, signed images, power-loss resilience, and staged fleet rollout. Use when building device update systems or reviewing one before it bricks a fleet.Votes: 0GitHub stars: 7
- Interrupt Safe CodeWrite ISRs that stay minimal, share data through volatile-correct handoffs, and defer real work safely. Use when writing interrupt handlers or debugging corruption that only happens sometimes.Votes: 0GitHub stars: 7
- Iot MessagingConnect device fleets with MQTT topic design, QoS chosen per message class, offline buffering, and safe fleet commands. Use when designing device-to-cloud messaging or debugging lost telemetry and stuck commands.Votes: 0GitHub stars: 7
- Low Power DesignReach battery-life targets through sleep-state budgeting, duty cycling, and measured (not estimated) current draw. Use when designing battery-powered devices or hunting a power regression.Votes: 0GitHub stars: 7
- Rtos Task DesignDecompose firmware into RTOS tasks with deadline-derived priorities, queue-based communication, and priority-inversion defenses. Use when structuring FreeRTOS/Zephyr-class applications or debugging missed deadlines.Votes: 0GitHub stars: 7
- Sensor Data HandlingTurn raw sensor readings into trustworthy data with correct sampling, filtering, calibration, and timestamped batching. Use when building sensor pipelines or debugging noisy, aliased, or drifting measurements.Votes: 0GitHub stars: 7
- Design SystemsBuild and maintain a design system that keeps a product visually consistent and fast to build. Use when creating design tokens, component libraries, or UI guidelines.Votes: 0GitHub stars: 7
- Error Boundaries UiIsolate render failures behind boundaries with useful fallbacks, retry, and reporting so one broken component does not blank the app. Use when adding error boundaries, designing failure UI, or a crash takes down a whole page.Votes: 0GitHub stars: 7
- Form HandlingBuild forms with validation timing, error display, and submission states that respect users and screen readers. Use when creating or reviewing any form, or fixing premature-error or lost-input complaints.Votes: 0GitHub stars: 7
- Frontend RoutingStructure client routes so the URL is the source of truth, data loads per route, and back/scroll behave. Use when adding routes, wiring route data loading, or fixing lost-filter or scroll-jump bugs.Votes: 0GitHub stars: 7
- Frontend StateDecide where frontend state lives and how it flows, so UIs stay predictable as they grow. Use when structuring components, adding state, or untangling prop-drilling and sync bugs.Votes: 0GitHub stars: 7
- List VirtualizationVirtualize long lists so only visible rows mount, with correct handling of dynamic heights and scroll anchoring. Use when a long list or table janks, or before building any list that can grow unbounded.Votes: 0GitHub stars: 7
- Optimistic UiApply optimistic updates with correct rollback, conflict handling, and pending cues so mutations feel instant without lying. Use when a mutation feels slow, or when adding or debugging optimistic updates and their rollbacks.Votes: 0GitHub stars: 7
- React Component DesignDesign React component props and boundaries so components compose cleanly and stay reusable. Use when creating a component, reviewing a bloated props list, or deciding controlled versus uncontrolled.Votes: 0GitHub stars: 7
- React Hooks DisciplineWrite React hooks with correct dependencies and minimal effects so renders stay predictable. Use when adding useEffect, debugging stale closures or render loops, or extracting a custom hook.Votes: 0GitHub stars: 7
- Ui State MachinesModel UI as explicit finite states so impossible combinations cannot render. Use when a component juggles interacting booleans, shows contradictory states, or a flow has grown too many flags to reason about.Votes: 0GitHub stars: 7
- Entity Component SystemModel game objects as entities with data components processed by systems, and know when ECS complexity pays. Use when structuring game architecture or escaping deep inheritance hierarchies.Votes: 0GitHub stars: 7
- Game Asset PipelineAutomate asset import, atlasing, compression, and hot reload so content flows from tools to game without hand steps. Use when building content pipelines or fixing bloated builds and stale assets.Votes: 0GitHub stars: 7
- Game Input HandlingBuild input systems with action mapping, buffering, dead zones, and rebinding that feel responsive and fair. Use when wiring game controls or fixing input that feels laggy or eats presses.Votes: 0GitHub stars: 7
- Game Loop ArchitectureStructure game loops with fixed-timestep simulation, interpolated rendering, and spiral-of-death protection. Use when building a game loop or fixing physics that behaves differently across frame rates.Votes: 0GitHub stars: 7
- Game PerformanceHold frame budgets through per-frame profiling, object pooling, draw-call batching, and allocation discipline. Use when a game stutters, drops frames, or needs optimization triage.Votes: 0GitHub stars: 7
- Game Save SystemsBuild save systems with versioned formats, corruption resistance, and autosave that never loses real progress. Use when designing game persistence or debugging broken saves after updates.Votes: 0GitHub stars: 7
- Multiplayer NetcodeBuild multiplayer with an authoritative server, client prediction, reconciliation, and lag compensation. Use when adding networking to a game or fixing rubber-banding and desync.Votes: 0GitHub stars: 7
- Procedural GenerationGenerate game content with seeded determinism, layered noise, constraint solving, and validation that guarantees playability. Use when building procedural levels, worlds, or loot, or debugging generation that breaks.Votes: 0GitHub stars: 7
- Branch StrategyChoose a branching model, default to trunk-based with short-lived branches, and set protection rules. Use when establishing team git workflow or fixing long-lived-branch merge pain.Votes: 0GitHub stars: 7
- Code OwnersDesign CODEOWNERS to route reviews and balance load without turning ownership into a gatekeeping bottleneck. Use when setting up review routing or fixing slow reviews and unclear responsibility.Votes: 0GitHub stars: 7
- Commit MessagesWrite commit messages that explain change and intent so history stays useful. Use when committing work or asked to draft a commit message for a diff.Votes: 0GitHub stars: 7
- Git History HygieneKeep git history atomic, bisectable, and readable with curated commits and disciplined force-push. Use when commits are messy, history is hard to navigate, or bisect and blame mislead.Votes: 0GitHub stars: 7
- Git Hooks AutomationAutomate checks with git hooks that stay fast, with server-side enforcement and documented escape hatches. Use when setting up pre-commit checks or fixing hooks that developers routinely bypass.Votes: 0GitHub stars: 7
- Git WorkflowUse git safely and legibly: branches, history, merges, conflicts, and recovery. Use when managing branches, cleaning history, resolving conflicts, or undoing mistakes.Votes: 0GitHub stars: 7
- Merge Vs RebaseChoose merge or rebase by the history you want, use interactive rebase safely, and set a team policy. Use when deciding integration mechanics or resolving debates about git history style.Votes: 0GitHub stars: 7
- Monorepo Vs PolyrepoDecide between one repository and many by tooling readiness, coupling, and team autonomy, and plan the migration. Use when structuring repositories for multiple projects or reconsidering a painful split.Votes: 0GitHub stars: 7
- Pull Request SizeKeep pull requests small through vertical slicing and stacking, because review quality and latency both collapse with size. Use when PRs are too big to review well or sit for days.Votes: 0GitHub stars: 7
- Release TaggingTag releases with semantic versions and signed tags, generate changelogs, and trigger builds from tags. Use when setting up a release process or fixing ambiguous, unsigned, or manual releases.Votes: 0GitHub stars: 7
- Actions SecurityPrevent workflow automation from becoming an attack path, through pinned actions, scoped tokens, and careful handling of untrusted input. Use when workflows handle secrets or run on pull requests from forks.Votes: 0GitHub stars: 7
- Branch ProtectionConfigure rules that stop unreviewed or broken code reaching the default branch, without making routine work impossible. Use when setting up a shared repository or after an incident traced to a direct push.Votes: 0GitHub stars: 7
- Dependency Scanning SetupConfigure automated dependency and vulnerability scanning at a cadence people will actually act on. Use when dependencies drift or vulnerabilities go unnoticed.Votes: 0GitHub stars: 7
- Github Actions WorkflowsWrite CI workflows that are fast, readable, and cheap, with the right triggers, caching, and matrix strategy. Use when setting up or fixing automation on a repository.Votes: 0GitHub stars: 7
- Github Api AutomationScript repository operations reliably, respecting rate limits, pagination, and permissions. Use when managing repositories at scale or building tooling around the platform.Votes: 0GitHub stars: 7
- Issue And Project TrackingStructure issues, labels, and boards so the tracker reflects reality and answers what is being worked on. Use when the backlog has grown beyond what anyone reads.Votes: 0GitHub stars: 7
- Pr AutomationAutomate the mechanical parts of pull requests, such as labelling, assignment, checks, and merging, so review effort goes to the code. Use when review process consumes attention on bookkeeping.Votes: 0GitHub stars: 7
- Release AutomationAutomate tagging, building, and publishing releases so shipping is repeatable and the artefacts match the tag. Use when releases are manual, inconsistent, or occasionally wrong.Votes: 0GitHub stars: 7