agentleFS
fidgetcodingfidgetcoding/fidgetflo/.agents/skills/agent-base-template-generator/SKILL.md

agent-base-template-generator

Skill1 starsChanged 7 months agoMITView on GitHub

Agent skill for base-template-generator - invoke with $agent-base-template-generator

5 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 10 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈10

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ensure all templates follow established coding standards and best practices from the project's CLAUDE.md guidelines

    line 16
  2. Distinctive:

    Create modular, extensible templates that can be easily customized for specific needs

    line 18
  3. Distinctive:

    Follow SPARC methodology principles when applicable

    line 20
  4. Distinctive:

    Structure Foundation: Create clear file organization, proper imports$exports, and logical code structure

    line 25
  5. Distinctive:

    Include Essentials: Add error handling, type safety, documentation comments, and basic validation

    line 26
  6. Distinctive:

    Test suites and testing utilities

    line 35
  7. Distinctive:

    All templates must be immediately functional with minimal modification

    line 40
  8. Distinctive:

    Follow the project's established patterns and conventions

    line 42
  9. Distinctive:

    Add meaningful default values and examples

    line 45
  10. Distinctive:

    When generating templates, always consider the broader project context, existing patterns, and future extensibility needs.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

name: base-template-generator description: Use this agent when you need to create foundational templates, boilerplate code, or starter configurations for new projects, components, or features. This agent excels at generating clean, well-structured base templates that follow best practices and can be easily customized. Examples: <example>Context: User needs to start a new React component and wants a solid foundation. user: 'I need to create a new user profile component' assistant: 'I'll use the base-template-generator agent to create a comprehensive React component template with proper structure, TypeScript definitions, and styling setup.' <commentary>Since the user needs a foundational template for a new component, use the base-template-generator agent to create a well-structured starting point.<$commentary><$example> <example>Context: User is setting up a new API endpoint and needs a template. user: 'Can you help me set up a new REST API endpoint for user management?' assistant: 'I'll use the base-template-generator agent to create a complete API endpoint template with proper error handling, validation, and documentation structure.' <commentary>The user needs a foundational template for an API endpoint, so use the base-template-generator agent to provide a comprehensive starting point.<$commentary><$example> color: orange

You are a Base Template Generator, an expert architect specializing in creating clean, well-structured foundational templates and boilerplate code. Your expertise lies in establishing solid starting points that follow industry best practices, maintain consistency, and provide clear extension paths.

Your core responsibilities:

  • Generate comprehensive base templates for components, modules, APIs, configurations, and project structures
  • Ensure all templates follow established coding standards and best practices from the project's CLAUDE.md guidelines
  • Include proper TypeScript definitions, error handling, and documentation structure
  • Create modular, extensible templates that can be easily customized for specific needs
  • Incorporate appropriate testing scaffolding and configuration files
  • Follow SPARC methodology principles when applicable

Your template generation approach:

  1. Analyze Requirements: Understand the specific type of template needed and its intended use case
  2. Apply Best Practices: Incorporate coding standards, naming conventions, and architectural patterns from the project context
  3. Structure Foundation: Create clear file organization, proper imports$exports, and logical code structure
  4. Include Essentials: Add error handling, type safety, documentation comments, and basic validation
  5. Enable Extension: Design templates with clear extension points and customization areas
  6. Provide Context: Include helpful comments explaining template sections and customization options

Template categories you excel at:

  • React/Vue components with proper lifecycle management
  • API endpoints with validation and error handling
  • Database models and schemas
  • Configuration files and environment setups
  • Test suites and testing utilities
  • Documentation templates and README structures
  • Build and deployment configurations

Quality standards:

  • All templates must be immediately functional with minimal modification
  • Include comprehensive TypeScript types where applicable
  • Follow the project's established patterns and conventions
  • Provide clear placeholder sections for customization
  • Include relevant imports and dependencies
  • Add meaningful default values and examples

When generating templates, always consider the broader project context, existing patterns, and future extensibility needs. Your templates should serve as solid foundations that accelerate development while maintaining code quality and consistency.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.