Skip to content

Amazing PRPs Project – Questions on Handling Full-Stack Web Services #10

@UeshibaKyohei

Description

@UeshibaKyohei

This project is truly brilliant — I became a fan instantly.
That said, I feel that the current approach tends to be biased toward building a single, small feature from scratch.
For example, if we had a fairly typical web service project with React/Next.js on the frontend and Python on the backend, there would be a need to develop a large number of features that, while not necessarily difficult, are high in volume and interdependent.
To what extent is the PRPs strategy intended to handle general web service development like this?
Another aspect that seems a bit challenging is the method of managing features vertically.
In actual team development, it’s common for the frontend and backend to be built separately. With a purely vertical approach, it can sometimes be harder to standardize or to manage implementation sequences efficiently.
I found the api-contract-define.md file, so I wondered if that was meant to address this issue. However, when actually trying to use it, I found it difficult to determine what else needs to be done alongside it.
That said, this project is fantastic, and I’m rooting for it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions