I once managed a small team and hired an intern to develop the backend services for a software system. He used AI tools to write the entire project; while it ran correctly and produced the right results, the directory structure was atrocious upon review. Typically, a FastAPI service is organized into components like routers and services, but he had created an unnecessarily deep, multi-layered structure within the service layer—logic that should have simply been split across two or three files. The code lacked elegance. Recalling concepts from books on software project management, code structure, and architecture—such as The Mythical Man-Month—I decided to codify these architectural principles into a reusable skill to optimize my project s structure. I used Claude Code to create a skill called `brooks-lint` and employed it to refactor the project, resulting in a much clearer and more logical architecture. I encourage everyone to use this skill, identify issues, submit pull requests, and collaborate on improvements, thereby benefiting the projects you are currently developing.