learn-factory

Scan codebases for factory patterns and generate knowledge_factory.md files.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/minhquan2904/vibe-check-scam --skill learn-factory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learn-factory
Source: https://github.com/minhquan2904/vibe-check-scam/tree/main/.agent/skills/learn-factory
Command: npx skills add https://github.com/minhquan2904/vibe-check-scam --skill learn-factory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically collects and documents factory pattern DNA from a codebase to enable consistent reuse by large language models.

Core Features & Use Cases

  • Scan for factory base classes and implementations across modules.
  • Capture constructor injections, generic type parameters, interfaces, and cache/invalidation patterns.
  • Produce a structured knowledge file (knowledge_factory.md) for LLMS and downstream tooling.

Quick Start

Inspect the project root to identify factory patterns and run the analysis to emit knowledge_factory.md to the designated output directory.

Frequently Asked Questions about learn-factory

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

FAQPage Schema
How do I document factory patterns in a codebase for LLM reuse?

To document factory patterns for LLM reuse, scan your codebase to discover base classes, implementations, and interfaces, then generate a structured knowledge file capturing constructor injections, generic type parameters, and cache patterns. This produces an exact map of signatures for downstream tooling.

What is a factory pattern knowledge file and how does it help code analysis?

A factory pattern knowledge file is a structured markdown document mapping factory base classes and implementations with exact names, packages, and signatures. It helps code analysis by providing consistent, reusable context for large language models to understand and apply design patterns accurately.

Can I scan a specific module scope to identify factory design patterns?

Yes, you can scan a specified module scope to identify factory design patterns. The analysis targets base classes and implementations within the defined scope, capturing constructor injections, generic type parameters, key methods, and cache or invalidation patterns for precise documentation.

What's the best way to extract constructor injections and generic type parameters from factory implementations?

The best way to extract constructor injections and generic type parameters is by scanning the codebase for factory base classes and implementations. This process captures exact signatures, interfaces, and cache or invalidation patterns, outputting the structured data into a markdown knowledge file.

Does this factory pattern documentation tool work without external dependencies?

Yes, the factory pattern documentation tool works without external dependencies. It directly inspects the project root, discovers factory patterns, and emits the knowledge file to your designated output directory without requiring additional components or setup.