agentshield Development Patterns

Standardize agentshield TypeScript development with naming, import, export, and commit conventions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/TGambit65/agentshield-dual-model --skill agentshield-development-patterns-tgambit65
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentshield Development Patterns
Source: https://github.com/TGambit65/agentshield-dual-model/tree/main/.agents/skills/agentshield
Command: npx skills add https://github.com/TGambit65/agentshield-dual-model --skill agentshield-development-patterns-tgambit65

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the confusion that contributors face when they don’t know AgentShield’s established conventions for file structure, exports, commits, and how to write and run tests consistently.

Core Features & Use Cases

  • Coding Conventions: Standardizes file naming (camelCase), import style (relative), and module exports (named exports) to keep the codebase uniform.
  • Workflow Guidance: Provides a repeatable feature-development process, including branching, implementing changes, adding/updating tests, and using Conventional Commits with the feat prefix.
  • Testing Patterns: Clarifies the expected test-file naming convention (.test.) and how to think about locating and validating tests before merging.

Quick Start

Ask the skill to guide your next change by telling it to follow the agentshield Development Patterns for file naming, exports, commit message format, and writing a matching .test. file.

Frequently Asked Questions about agentshield Development Patterns

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

FAQPage Schema
What TypeScript conventions should I follow for file naming and module exports?

TypeScript conventions for this codebase require camelCase file naming, relative imports, and named exports to maintain structural uniformity across modules and contributors.

How do I structure a feature workflow with Conventional Commits in a TypeScript repository?

Feature workflow involves branching, implementing changes, adding tests, and committing using Conventional Commits with the feat prefix to ensure repeatable and traceable development cycles.

What is the correct naming pattern for unit test files in a TypeScript project?

Unit test files must follow the *.test.* naming pattern, ensuring tests are easily located and executed during the project's test run procedure before merging changes.

How do I write and run tests consistently when adding new TypeScript modules?

Writing and running tests consistently requires creating a matching *.test.* file alongside your new module and executing the project's designated test run procedure to validate functionality.

Does this development pattern enforce relative imports over absolute paths for TypeScript?

Yes, the development pattern enforces relative imports over absolute paths to standardize module resolution and keep the codebase uniform across all contributor workflows.

When should I use the feat prefix for Conventional Commits during feature development?

Use the feat prefix for Conventional Commits whenever introducing new functionality or modules, signaling a new feature addition to the codebase during your development workflow.