create-import-module

Create a .plain file with YAML frontmatter for shared concepts and requirements.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/Codeplain-ai/onboarding-flow --skill create-import-module
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-import-module
Source: https://github.com/Codeplain-ai/onboarding-flow/tree/main/.claude/skills/create-import-module
Command: npx skills add https://github.com/Codeplain-ai/onboarding-flow --skill create-import-module

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the need for creating a plain import module that contains shared definitions, implementation requirements, and test requirements for other modules to import.

Core Features & Use Cases

  • Shared Definitions: Create a new .plain file with definitions for concepts that can be reused across multiple modules.
  • Implementation Requirements: Provide common implementation requirements such as technology stack and coding standards.
  • Test Requirements: Offer common test requirements for consistency across modules.
  • Use Case: When you need to create a foundational structure for other modules to import, ensuring consistency and reusability of code.

Quick Start

Use the create-import-module skill to create a new import module named 'common-utils' in the 'template/' directory.

Frequently Asked Questions about create-import-module

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

FAQPage Schema
How do I create a shared import module for reusable code definitions?▼

To create a shared import module, you construct a .plain file containing YAML frontmatter and specific content sections for shared definitions, implementation requirements, and test requirements to ensure code reuse.

What is a plain import module used for in software development?▼

A plain import module provides a foundational structure for defining shared concepts, technology stack standards, and test requirements that other modules can import to maintain consistency.

How do I define common implementation requirements for multiple modules?▼

You define common implementation requirements by creating a .plain file with YAML frontmatter, adding sections for coding standards and technology stacks that other modules can directly import.

Can I standardize test requirements across different modules using a .plain file?▼

Yes, you can standardize test requirements by generating a plain import module that specifies common testing criteria, ensuring consistency across all modules that import the file.

What's the best way to structure shared definitions for modularization?▼

The best way to structure shared definitions is using a plain import module with YAML frontmatter, separating concepts, implementation requirements, and test requirements into distinct content sections.

When do I need to create a plain import module instead of standard code files?▼

You need a plain import module when you require a centralized foundational structure for shared definitions and requirements, ensuring reusability and consistency across multiple software modules.