import-conventions

Enforces import path and module boundary rules in TypeScript/JavaScript projects.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/twlines/maslow --skill import-conventions-twlines
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: import-conventions
Source: https://github.com/twlines/maslow/tree/main/skills/import-conventions
Command: npx skills add https://github.com/twlines/maslow --skill import-conventions-twlines

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill establishes and enforces clear rules for how code modules should import from each other, preventing common issues like circular dependencies and improving code maintainability.

Core Features & Use Cases

  • File Extension Consistency: Ensures all import paths use .js for uniformity.
  • Module Boundary Enforcement: Defines strict rules for imports between src/, apps/*, and packages/*.
  • Style Guidelines: Promotes best practices like avoiding barrel exports and grouping imports.
  • Use Case: When developing a new feature, this Skill ensures your code adheres to the project's established import structure, preventing potential build errors and making the codebase easier to navigate for all developers.

Quick Start

Apply the import conventions to the current codebase.

Frequently Asked Questions about import-conventions

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

FAQPage Schema
How do I enforce import path and module boundary rules in a TypeScript project?

You can enforce import path and module boundary rules by applying automated conventions that govern inter-directory dependencies and import syntax. This prevents circular dependencies and ensures adherence to established style guides within your TypeScript project.

What is the best way to prevent circular dependencies in JavaScript codebases?

Preventing circular dependencies involves establishing strict module boundaries between directories like src, apps, and packages. Enforcing clear import rules and avoiding barrel exports improves code maintainability and stops potential build errors.

How do I ensure file extension consistency for import paths in JavaScript?

To ensure file extension consistency for import paths, apply rules that require all imports to use the .js extension. This uniformity across your JavaScript project makes the codebase easier to navigate and prevents module resolution issues.

Can I enforce specific style guidelines for type imports and barrel exports?

Yes, you can enforce style guidelines that promote best practices like grouping imports and avoiding barrel exports. Governing import syntax and type imports ensures adherence to established style guides and common package usage patterns.

Why does my TypeScript project fail to resolve modules with inconsistent import structures?

Modules fail to resolve when import structures lack consistency in file extensions and inter-directory dependencies. Enforcing strict module boundaries and uniform .js import paths prevents these potential build errors and improves code maintainability.