agentsclimarketplace

Conversion copywriting engine

Skill imMamdouhaboammar/conversion-copywriting-engine/.agents/skills/conversion-copywriting-engine

Complete conversion copywriting operating system for Claude. Supports TTPM, FAB&M, Persuasion Cards, TOF/MOF/BOF messaging, and CRO quality gates.From the repository description

Install
npx -y skills add imMamdouhaboammar/conversion-copywriting-engine --skill conversion-copywriting-engine

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.6 KB, as published. Nobody here has run it

# conversion-copywriting-engine Development Patterns

> Auto-generated skill from repository analysis

## Overview
This skill teaches you the core development patterns, coding conventions, and workflows used in the `conversion-copywriting-engine` TypeScript codebase. You'll learn how to structure files, write imports/exports, follow commit conventions, and manage testing, ensuring consistency and maintainability throughout the project.

## Coding Conventions

### File Naming
- Use **kebab-case** for all file names.
  - Example:  
    ```
    conversion-utils.ts
    copywriting-engine.test.ts
    ```

### Import Style
- Use **relative imports** for referencing local modules.
  - Example:
    ```typescript
    import { generateCopy } from './copy-generator';
    ```

### Export Style
- Use **named exports** instead of default exports.
  - Example:
    ```typescript
    // In copy-generator.ts
    export function generateCopy(input: string): string { ... }
    ```

### Commit Messages
- Follow **conventional commit** format.
- Use prefixes like `docs` for documentation changes.
  - Example:
    ```
    docs: update README with usage examples
    ```

## Workflows

### Code Contribution
**Trigger:** When adding or updating code in the repository  
**Command:** `/contribute`

1. Create or update files using kebab-case naming.
2. Use relative imports for all internal modules.
3. Export functions or variables using named exports.
4. Write clear, conventional commit messages (e.g., `docs: add usage guide`).
5. If applicable, add or update corresponding test files.

### Testing
**Trigger:** When verifying code correctness or before submitting a pull request  
**Command:** `/test`

1. Locate or create test files matching the `*.test.*` pattern.
2. Write tests for new or changed functionality.
3. Run the tests using the project's preferred test runner (framework is currently unknown; check project documentation or scripts).
4. Ensure all tests pass before committing changes.

## Testing Patterns

- Test files are named using the `*.test.*` pattern (e.g., `copywriting-engine.test.ts`).
- The specific testing framework is not detected; refer to the project documentation or package.json for details.
- Place tests close to the code they validate, following the same kebab-case naming convention.

## Commands
| Command      | Purpose                                              |
|--------------|------------------------------------------------------|
| /contribute  | Step-by-step guide for contributing code             |
| /test        | Instructions for writing and running tests           |

Keep looking

Skills are one crate of 609,689. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.