“writing” 共 777 个结果
io.github.affaan-m/ECC/django-tdd
Django testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs. Use when writing Django or DRF tests with pytest-django, or driving a Django feature test-first.
io.github.affaan-m/ECC/csharp-testing
C# and .NET testing patterns with xUnit, FluentAssertions, mocking, integration tests, and test organization best practices. Use when writing or reviewing xUnit tests, mocks, or integration tests in a C# / .NET project.
io.github.affaan-m/ECC/perl-testing
Perl testing patterns using Test2::V0, Test::More, prove runner, mocking, coverage with Devel::Cover, and TDD methodology. Use when writing Perl tests with Test2::V0 or Test::More, or measuring coverage.
io.github.affaan-m/ECC/rust-testing
Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology. Use when writing Rust tests — unit, integration, async, property-based, or coverage.
io.github.affaan-m/ECC/fsharp-testing
F# testing patterns with xUnit, FsUnit, Unquote, FsCheck property-based testing, integration tests, and test organization best practices. Use when writing F# tests with xUnit, FsUnit, Unquote, or FsCheck.
io.github.affaan-m/ECC/kotlin-testing
Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices. Use when writing Kotlin tests with Kotest or MockK, or testing coroutines and checking coverage.
io.github.affaan-m/ECC/golang-testing
Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices. Use when writing Go tests — table-driven cases, subtests, benchmarks, fuzzing, or coverage.
io.github.affaan-m/ECC/e2e-testing
Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies. Use when writing Playwright tests, structuring page objects, or fixing flaky E2E runs in CI.
io.github.affaan-m/ECC/cpp-testing
Use only when writing/updating/fixing C++ tests, configuring GoogleTest/CTest, diagnosing failing or flaky tests, or adding coverage/sanitizers.
io.github.affaan-m/ECC/python-patterns
Pythonic idioms, PEP 8 standards, type hints, and best practices for building robust, efficient, and maintainable Python applications. Use when writing or reviewing Python code and idiomatic structure, typing, or PEP 8 is in question.
io.github.affaan-m/ECC/prisma-patterns
Prisma ORM patterns for TypeScript backends — schema design, query optimization, transactions, pagination, and critical traps like updateMany returning count not records, $transaction timeouts, migrate dev resetting the DB, @updatedAt skipped on bulk writes, and serverless connection exhaustion. Use when writing a Prisma schema or query, or debugging transactions, migrations, or serverless connection limits.
io.github.affaan-m/ECC/java-coding-standards
Java coding standards for Spring Boot and Quarkus services: naming, immutability, Optional usage, streams, exceptions, generics, CDI, reactive patterns, and project layout. Automatically applies framework-specific conventions. Use when writing or reviewing Java in a Spring Boot or Quarkus service.
io.github.affaan-m/ECC/react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
io.github.affaan-m/ECC/react-testing
React component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress end-to-end runs. Use when writing or fixing tests for React components, hooks, or pages.
io.github.affaan-m/ECC/react-performance
React and Next.js performance optimization patterns adapted from Vercel Engineering's React Best Practices (https://github.com/vercel-labs/agent-skills). Organizes 70+ rules across 8 priority categories — waterfalls, bundle size, server-side, client fetching, re-render, rendering, JS micro-perf, advanced. Use when writing, reviewing, or refactoring React/Next.js code for performance.
io.github.wshobson/agents/modern-javascript-patterns
掌握 ES6+ 特性，包括 async/await、解构、展开运算符、箭头函数、Promise、模块、迭代器、生成器与函数式编程模式，编写简洁高效的 JavaScript 代码。在重构遗留代码、实现现代模式或优化 JavaScript 应用时使用。
io.github.deepseek-ai/deepseek-harness/agent-experience
Use when writing or changing a model-facing tool definition (name, description, parameter schema, or its system-prompt section), and when designing skills, context loading, or multi-step workflows, to make information discoverable and use context efficiently.
io.github.affaan-m/ECC/competitive-report-structure
Assemble scored competitor profile cards (from benchmark-methodology) into a decision-grade competitive report with landscape map, competitor tiers, benchmarking matrix, white-space analysis, strategic recommendations, and team alignment trigger questions. Use when presenting competitive findings to leadership or a board, writing a competitive landscape report, or as the final step of the competitive analysis pipeline.
io.github.affaan-m/ECC/tdd-workflow
在编写新功能、修复 bug 或重构代码时使用此 skill。强制推行测试驱动开发，覆盖率不低于 80%，涵盖单元、集成与 E2E 测试。
io.github.affaan-m/ECC/dart-flutter-patterns
可用于生产的 Dart 与 Flutter 模式，覆盖空安全、不可变状态、异步组合、Widget 架构、主流状态管理框架（BLoC、Riverpod、Provider）、GoRouter 导航、Dio 网络、Freezed 代码生成与整洁架构。在编写或评审 Dart 与 Flutter 代码——状态、Widget、导航、网络或架构——时使用。
io.github.affaan-m/ECC/search-first
先检索再编码的工作流。在动手编写自定义代码之前，先搜索已有的工具、库和模式。会调用 researcher 代理。
io.github.affaan-m/ECC/inherit-legacy-style
遗留项目风格继承 skill。当用户输入 /inherit-legacy-style，或需要让 AI 编码代理接手手写遗留项目并防止“风格漂移”（模型把自身预训练的主流惯用法强加给项目）时使用。与语言和框架无关——只对齐元架构，不改语法。一旦运行，它就成为后续所有编码任务的行为约束。不要用于纯研究或与代码风格对齐无关的一次性提问。
io.github.affaan-m/ECC/loop-design-check
设计以目标为导向的 Agent 循环，并排查循环常见的出错方式——原地打转烧 token、钻验证器的空子（Goodhart 效应）、把错误答案一路跑到底。包含两个动作：(1) 编写循环——先判断是否值得构建、定义机器可判定的目标、选定循环类型与脚手架；(2) 审查循环——按五种失败模式，加上可判定性、边界、兜底方案、评判者独立性，以及把判断权留在人手中这条红线逐项检查。当设计自主 Agent 循环，或已有循环但担心它跑飞、作弊或把错误答案执行到底时使用。它在机制层循环技能（autonomous-loops、continuous-agent-loop）之外补足其未覆盖的判断层。中文触发：写 loop、设计 loop、做一个 loop、检查 loop 对不对、loop 体检、loop 会不会跑飞、可判定目标、五个崩法、plan build judge。English triggers: design an agent loop, write a loop, check a loop, loop review, prevent a runaway loop, goal-oriented loop, decidable goal, plan/build/judge.
io.github.affaan-m/ECC/git-workflow
Git 工作流模式，包括分支策略、提交约定、合并与变基的取舍、冲突解决，以及适用于各种规模团队的协作开发最佳实践。当需要选择分支策略、制定提交约定、决定用 merge 还是 rebase，或解决冲突时使用。
