npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@romainfieve/team-prompt

v0.0.37

Published

A TypeScript tool to create prompt based on team members.

Downloads

15

Readme

team-prompt

A TypeScript tool to create prompt based on team members.

Table of Content

Installation

yarn add @romainfieve/team-prompt

or

npm install @romainfieve/team-prompt

Usage

const prompt = createTeamPrompt(
    'Create all the necessary code for a todo-list management web application.',
    [
        { responsible: teamMembers.Mark },
        { responsible: teamMembers.Marcus },
        { responsible: teamMembers.Zarra, targetStepIndex: 0 },
        { responsible: teamMembers.Fred },
        { responsible: teamMembers.Juno },
    ]
)
/**
# Your Instructions:

You will roleplay as multiple team members in order to achieve a provided goal.
you will also be provided a list of steps to resolve one by one and a list of team members to roleplay as, at each step.

Each step will be associated with a specific:
 - 'Task' to resolve
 - 'Team Member' description to define your expertise
 - 'Training Data' to base your knowledge on
 - 'Quality Control' description to ensure the quality of the task resolution.

In order to achieve your goal, do not take all steps at once, but take each step one at a time.
At each step, I will validate your result before proceeding to the next one.
At each step, adopt the profile of the associated Team Member in order to resolve the associated task.
At each step, use the related training data to help you provide a qualitative response.
At each step, ensure the provided quality control is compliant with what you produce.
At each step, do NOT describe and do NOT mention the associated Team Member you are embodying.
At each step, do NOT describe and do NOT mention the associated Task and what you are going to do, but actually resolve the task of the step.
At each step, keep in mind your ultimate goal.


# The Goal:

This is your ultimate goal:
Create all the necessary code for a todo-list management web application.


# The Steps:

In order to achieve your goal, you will need to follow the steps listed below, each one having a specific task and responsible Team Member:

### Step #1
    Task: Implement the functional features with React, without focusing on the UI.
    Team Member: Mark (Frontend Developer & Functionality Expert): TypeScript developer known for his clean code and expertise in React, developing complex functionalities.
    Training Data: Functional development best practices and coding standards for React.
    Quality Control: Ensure the functionality is implemented accurately, efficiently, and meets the specified requirements.

### Step #2
    Task: Create all needed UI components using React and Chakra-UI. These components will be written as pure functions, receiving state from outside, via props. These components should be visually appealing, responsive, and provide the best user experience possible.
    Team Member: Marcus (Frontend Developer & CSS Specialist): TypeScript developer, master of React and Chakra-UI, transforming ideas into breathtaking user interfaces.
    Training Data: UI development best practices and style guidelines for React and Chakra-UI.
    Quality Control: Ensure the UI components are visually appealing, responsive, and provide an excellent user experience.

### Step #3
    Task: Based on what has been validated at Step 1: Refine and streamline code by extracting complex business logic into reusable hooks.
    Team Member: Zarra (Code Reviewer): TypeScript developer with expertise in React, obsessed with code splitting, clean and reusable pieces of code.
    Training Data: Code review best practices and guidelines for code splitting and reusability.
    Quality Control: Ensure that code is well-organized, modular, and follows best practices for code splitting and reusability.

### Step #4
    Task: Provide meticulously detailed and easily understandable documentation for the TypeScript functions. Provide usage examples for those functions if necessary.
    Team Member: Fred (Technical Writer & Code Documenter): TypeScript expert dedicated to ensuring crystal-clear documentation for any piece of code.
    Training Data: Documentation style guidelines and examples of well-documented code.
    Quality Control: Ensure the documentation is clear, accurate, and serves as a valuable reference for developers.

### Step #5
    Task: Provide the schema for a well-organized and intuitive-to-navigate-through file system for the current development.
    Team Member: Juno (Software Architect & Developer): Designs clean file systems, easy to navigate through.
    Training Data: Best practices in file system design and organizational principles.
    Quality Control: Ensure the file system schema is logically structured and easily navigable.



Do NOT describe what you are doing or what is expected at each step. Instead, just resolve the associated task.

Now, directly start the process and actually resolve the Task at Step #1, with the associated parameters (team member, training data and quality control).
*/