AI-Coding-Guidance-Skills Development Patterns

Standardize Python feature implementation, tracking, semantic review, and test updates.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kileroppo/AI-Coding-Guidance-Skills --skill ai-coding-guidance-skills-development-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: AI-Coding-Guidance-Skills Development Patterns
Source: https://github.com/kileroppo/AI-Coding-Guidance-Skills/tree/main/.agents/skills/AI-Coding-Guidance-Skills
Command: npx skills add https://github.com/kileroppo/AI-Coding-Guidance-Skills --skill ai-coding-guidance-skills-development-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces contributor friction by standardizing the conventions, feature-tracking workflow, and test/coverage practices used in AI-Coding-Guidance-Skills.

Core Features & Use Cases

  • Coding Conventions: Enforces consistent file naming, import style, and export patterns so new modules blend into the existing codebase.
  • Feature Development with Tracking: Guides contributors to create/update feature implementation and mirror progress in the repository’s feature JSON files.
  • Test & Review Loops: Provides repeatable patterns for increasing test coverage and running a semantic review → fix → validate cycle.
  • Use Case: When adding a new kernel capability, use this Skill to implement the change, register it in the tracked FEAT-XXX record, and ship with a matching test update.

Quick Start

Ask your AI assistant: “Help me add a new feature to AI-Coding-Guidance-Skills and update the corresponding FEAT-XXX tracking file plus tests following the repository development patterns.”

Frequently Asked Questions about AI-Coding-Guidance-Skills Development Patterns

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

FAQPage Schema
How do I standardize Python feature implementation and tracking for new module additions?

Standardize Python feature implementation by enforcing kebab-case naming, relative imports, and named export conventions, while tracking progress in feature JSON artifacts. This ensures new modules blend seamlessly into the existing codebase and maintain consistent tracking.

What is the best way to automate Conventional Commits messaging and feature tracking in a Python workflow?

Automate Conventional Commits messaging and feature tracking by coordinating feature implementation with task state updates via JSON artifacts. This workflow standardizes contributor messaging and mirrors progress directly in the repository's tracking files.

How do I run a semantic review and fix cycle to expand test coverage for Python modules?

Run a semantic review and fix cycle to expand test coverage by following repeatable patterns for validating Python modules. This workflow provides a structured review, fix, and validate loop to ensure comprehensive test updates for new capabilities.

Does this development pattern workflow require specific Python import and export conventions?

Yes, this development pattern workflow requires Python modules to use relative imports and named export conventions. Enforcing these specific coding conventions alongside kebab-case file naming guarantees that new kernel additions integrate smoothly.

When do I need to update feature JSON artifacts during an iterative improvement cycle?

Update feature JSON artifacts during iterative improvement cycles whenever delivering new capabilities, expanding coverage, or completing review-fix remediation. This maintains accurate task and feature state tracking across the repository.