All authors
Claude Skills by nimadorostkar
github.com/nimadorostkar138 skills5 installs181 views
- CppUse when writing modern C++ (17/20/23). Covers RAII, smart-pointer ownership, move semantics, ranges, concepts, and eliminating undefined behavior with sanitizers.Votes: 0GitHub stars: 26
- Csharp DotnetUse when building on .NET 8+ with C# 12. Covers nullable reference types, records, async/await correctness, minimal APIs, dependency injection, and EF Core query performance.Votes: 0GitHub stars: 26
- GoUse when writing Go services, CLIs, or libraries. Covers idiomatic error wrapping, goroutine and context discipline, interface design, table-driven tests, and the race detector.Votes: 0GitHub stars: 26
- Java KotlinUse when writing modern Java (17+) or Kotlin on the JVM. Covers records, sealed interfaces, pattern matching, coroutines, null safety, and JVM performance and memory tuning.Votes: 0GitHub stars: 26
- PhpUse when writing PHP 8.2+ or working in Laravel and Symfony codebases. Covers strict types, enums, readonly classes, attributes, PSR standards, and static analysis with PHPStan.Votes: 0GitHub stars: 26
- PythonUse when writing, reviewing, or modernizing Python 3.11+ code. Produces fully type-annotated modules, async I/O, dataclasses and protocols, pytest suites, and a lint/type gate built on ruff and mypy --strict.Votes: 0GitHub stars: 26
- RubyUse when writing Ruby or working in Rails codebases. Covers idiomatic object design, service objects, ActiveRecord query performance, RSpec structure, and RuboCop-clean style.Votes: 0GitHub stars: 26
- RustUse when writing Rust or resolving borrow-checker, lifetime, and trait errors. Covers ownership models, error handling with thiserror and anyhow, async with Tokio, and safe abstractions over unsafe code.Votes: 0GitHub stars: 26
- ShellUse when writing Bash scripts or command-line automation. Covers strict mode, safe quoting, argument parsing, trap-based cleanup, portability, and ShellCheck-clean scripts.Votes: 0GitHub stars: 26
- SqlUse when writing or optimizing SQL. Covers query planning, indexing strategy, window functions, CTEs, transaction isolation, and reading EXPLAIN output.Votes: 0GitHub stars: 26
- SwiftUse when writing Swift for iOS, macOS, or server-side. Covers value semantics, optionals, protocol-oriented design, structured concurrency with async/await and actors, and SwiftUI state management.Votes: 0GitHub stars: 26
- TypescriptUse when writing or hardening TypeScript in strict mode. Covers advanced types, discriminated unions, runtime validation at trust boundaries, generics, and removing `any` from an existing codebase.Votes: 0GitHub stars: 26
- FlutterUse when building Flutter applications. Covers widget composition, state management, build-method performance, platform channels, and the rendering behavior behind most Flutter jank.Votes: 0GitHub stars: 26
- IosUse when building native iOS applications. Covers SwiftUI architecture, state management, navigation, networking, persistence, background behavior, and App Store submission requirements.Votes: 0GitHub stars: 26
- Mobile ReleaseUse when preparing a mobile app for release. Covers versioning, signing, staged rollout, crash monitoring, store review requirements, and rollback when an update goes wrong.Votes: 0GitHub stars: 26
- React NativeUse when building cross-platform mobile apps with React Native or Expo. Covers navigation, platform differences, list performance, native modules, offline behavior, and release builds.Votes: 0GitHub stars: 26
- Deep ResearchUse when researching a question that requires multiple sources. Covers question decomposition, source evaluation, tracking what is known versus assumed, and producing a synthesis with honest confidence levels.Votes: 0GitHub stars: 26
- Fact CheckingUse when verifying claims. Covers tracing a claim to its origin, evaluating sources, detecting laundered statistics, and reporting a verdict with the evidence rather than an assertion.Votes: 0GitHub stars: 26
- File OrganizationUse when organizing, deduplicating, or cleaning up files. Covers safe classification and renaming, finding true duplicates, reclaiming space, and never destroying data during a cleanup.Votes: 0GitHub stars: 26
- Meeting NotesUse when turning a meeting, call, or transcript into notes. Covers extracting decisions and actions rather than transcribing discussion, and producing something that is useful a month later.Votes: 0GitHub stars: 26
- Web Data ExtractionUse when extracting data from web pages. Covers choosing between an API, static parsing, and a browser, handling JavaScript-rendered content, resilient selectors, rate limiting, and scraping responsibly.Votes: 0GitHub stars: 26
- Secrets ManagementUse when handling credentials, API keys, and certificates. Covers secret storage, rotation, injection into applications, detection of leaked secrets, and what to do when one is exposed.Votes: 0GitHub stars: 26
- Secure CodingUse when writing code that handles untrusted input, authentication, or sensitive data. Covers injection prevention, authentication and session handling, authorization, cryptography, and the defaults that make code safe by construction.Votes: 0GitHub stars: 26
- Security ReviewUse when auditing code or a change for vulnerabilities. Produces severity-ranked findings with exploit paths and fixes, covering the OWASP Top 10, authorization, secrets, and dependency risk.Votes: 0GitHub stars: 26
- Supply ChainUse when assessing dependency and build-pipeline risk. Covers dependency vetting, lockfiles, SBOMs, provenance and signing, pinning CI actions, and responding to a compromised package.Votes: 0GitHub stars: 26
- Threat ModelingUse when designing a system and identifying what could go wrong. Applies STRIDE to a data-flow model, ranks threats by realistic risk, and produces mitigations that are actually built.Votes: 0GitHub stars: 26
- E2e PlaywrightUse when writing end-to-end browser tests with Playwright. Covers resilient locators, auto-waiting, network interception, authentication reuse, parallelization, and eliminating flakiness.Votes: 0GitHub stars: 26
- Performance TestingUse when load testing a system. Covers workload modeling, ramp profiles, what to measure, finding the breaking point, and distinguishing a real bottleneck from a badly configured test.Votes: 0GitHub stars: 26
- Qa ReviewUse when reviewing a feature for release readiness. Covers acceptance-criteria verification, edge-case enumeration, regression risk assessment, and a release decision that is a judgment rather than a vibe.Votes: 0GitHub stars: 26
- Test Driven DevelopmentUse when practicing TDD. Covers the red-green-refactor loop, choosing the next test, designing through tests, and when TDD is and is not the right approach.Votes: 0GitHub stars: 26
- Test StrategyUse when deciding what to test and at which level. Covers the test pyramid, what belongs in unit versus integration versus end-to-end tests, coverage as a signal rather than a target, and eliminating flakiness.Votes: 0GitHub stars: 26
- Web App TestingUse when testing a web application interactively — verifying a feature, reproducing a bug, or checking a flow in a real browser. Covers systematic exploration, console and network inspection, and reporting what you find.Votes: 0GitHub stars: 26
- ChangelogUse when writing a changelog or release notes. Covers what belongs in one, writing for users rather than for git, semantic versioning, and documenting breaking changes so nobody is surprised.Votes: 0GitHub stars: 26
- EditingUse when editing prose for clarity and force. Covers cutting, structural editing, the specific constructions that weaken writing, and editing someone else's work without destroying their voice.Votes: 0GitHub stars: 26
- Internal CommsUse when writing an announcement, update, or memo for colleagues. Covers leading with the point, matching the format to the audience, and writing something people actually read.Votes: 0GitHub stars: 26
- Long Form ContentUse when writing a researched article, blog post, or long-form piece. Covers building an argument, researching and citing, structure, and writing something with a point rather than a survey.Votes: 0GitHub stars: 26
- Technical DocumentationUse when writing developer-facing documentation. Covers the four documentation types and choosing between them, writing a README, API reference, and tutorials that work.Votes: 0GitHub stars: 26
- TemplatesUse when <the situation, in the words a user would actually use>. Covers <scope>. Trigger on "<phrasing>", "<phrasing>". Do not use for <adjacent case> — see the <other> skill.Votes: 0GitHub stars: 26