skills.rest
affaan-m
affaan-mCOMMUNITY
Explore all skills by this author →
Website𝕏@affaanmustafaGitHub

agentshield Development Patterns

Standardize agentshield TypeScript contributions with camelCase files, named exports, and Conventional Commits.

1.1k|224|Updated Feb 11, 2026
Search Tags:#typescript#conventional commits#coding conventions#testing patterns#contribution workflow#named exports
One-click install
npx skills add https://github.com/affaan-m/agentshield --skill agentshield-development-patterns
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agentshield Development Patterns
Source: https://github.com/affaan-m/agentshield/tree/main/.agents/skills/agentshield
Command: npx skills add https://github.com/affaan-m/agentshield --skill agentshield-development-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps contributors consistently implement changes that match agentshield’s existing TypeScript architecture and collaboration conventions, reducing integration friction and review back-and-forth.

Core Features & Use Cases

  • Coding Conventions: Enforces camelCase file naming plus relative imports and named exports for module consistency.
  • Contribution Workflows: Guides feature development and testing using the repo’s defined trigger commands.
  • Testing Patterns: Encourages colocated test files using the *.test.* naming convention for predictable validation coverage.

Quick Start

Ask an AI assistant to apply the agentshield Development Patterns by creating camelCase TypeScript modules with named exports and adding an *.test.* file that matches the surrounding codebase conventions.

Frequently Asked Questions about agentshield Development Patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure TypeScript modules with named exports for repository contributions?▼

TypeScript module contributions require camelCase file naming, relative imports, and named exports to ensure module consistency across the repository and reduce review friction.

What is the conventional commits workflow for TypeScript contribution?▼

The conventional commits workflow standardizes feature development by enforcing specific commit message formats and defined trigger commands before merging repository changes.

How do I set up TypeScript test files using the *.test.* pattern?▼

TypeScript test files using the *.test.* pattern are colocated next to source files to provide predictable validation coverage matching surrounding codebase conventions during feature development.

Does this contribution workflow require relative imports for TypeScript modules?▼

Yes, the contribution workflow requires relative imports alongside camelCase file naming and named exports to maintain module consistency and minimize integration friction.

What are the limitations of applying standard coding conventions to existing TypeScript codebases?▼

Applying standard coding conventions like camelCase file naming and relative imports requires existing codebases to undergo structural refactoring, which may temporarily disrupt current workflows.

Related Skills

Explore More Software Engineering Skills→
MakisuoMakisuo
1.6k

clickhousectl-local-dev

Install and configure a local ClickHouse environment with clickhousectl.

Community
Intermediate
seasonedccseasonedcc
4

testing

Find and run Vitest-based unit tests in TypeScript projects.

Official
Intermediate
GaryOcean428GaryOcean428

import-resolution

Identify and fix Python import errors and validate __init__.py exports.

Community
Intermediate
JylhisJylhis
1

typescript-formatting

Enforce consistent TypeScript and JavaScript formatting with Prettier and ESLint.

Community
Intermediate