# Findy Library ## Get Started - [Findy Library](https://lib.findy.co.jp/index.md): A documentation site where Findy, Inc. shares its knowledge on a wide range of topics. - [Quickstart for AI agents: llms.txt, Markdown, and MCP](https://lib.findy.co.jp/quickstart.md): How an AI agent reads Findy Library: the llms.txt index, per-page Markdown, and the search MCP server. - [Terms of Service](https://lib.findy.co.jp/terms-of-service.md): The terms of service governing the use of Findy Library, the documentation site provided by Findy Inc. ## Development Basics - [How to write pull requests: templates, granularity, stacks](https://lib.findy.co.jp/development/pull-request.md): Pull request basics and practice: setting up a PR template, standardizing commit messages and titles, judging granularity, and stacks for dependent changes. - [How to do code review: what to check, how to comment](https://lib.findy.co.jp/development/code-review.md): Why code review matters, what to check for each type of requirement, how tooling has taken over the checking, how to self-review, the bar for approval, and how to write comments. - [How to break down tasks: one task, one pull request](https://lib.findy.co.jp/development/task-breakdown.md): Breaking work into small, independent units: benefits, good-task conditions, split-or-merge criteria, breakdown steps, dependencies, and issue creation. - [What is modifiability? Keeping software easy to change](https://lib.findy.co.jp/development/modifiability.md): Classify software changes into three kinds — separate, revise, and remove — and learn the patterns that break modifiability and how to prevent them. - [What is refactoring? Changing structure, not behavior](https://lib.findy.co.jp/development/refactoring.md): Change structure without changing behavior: separate structure from behavior changes, proceed in small reversible steps, and design code for deletion. - [How to improve web performance: order and judgment](https://lib.findy.co.jp/development/performance.md): The judgment that comes before individual techniques: why to improve web service performance, how fast is fast enough, and in what order to consider fixes. - [How to write test code that protects your system from bugs](https://lib.findy.co.jp/development/testing.md): Design tests that pass when they should and fail when they should, instead of chasing coverage numbers, so regressions surface before release. - [What is CI/CD? Building a fast, automated pipeline](https://lib.findy.co.jp/development/ci-cd.md): What a CI/CD pipeline provides, how to keep CI fast, automate releases, notify results, and treat deployment frequency as a metric. - [How to run Dependabot and Renovate without a PR backlog](https://lib.findy.co.jp/development/dependency-updates.md): Why dependencies should be updated continuously, how to handle automated update pull requests, how far to auto-merge, and how to delegate first-pass checks to an AI agent. - [Release strategy: separating deployment from release](https://lib.findy.co.jp/development/release-strategy.md): Separate deploying code from releasing features. Covers environment-variable feature flags, trunk-based development, gradual rollout, instant rollback, and flag cleanup. - [How to design alerts and notifications for dev teams](https://lib.findy.co.jp/development/notifications.md): Why detection time drives recovery time, what deserves a notification, and how to route alerts and development workflow events without wearing out the channel. ## Organization - [How to onboard new engineers so they can work autonomously](https://lib.findy.co.jp/organization/onboarding.md): How a team supports new engineers until they work autonomously: setting goals, sharing a checklist, preparing before day one, supporting the first month, and onboarding with AI agents. - [How to develop engineers: goals, feedback, staged learning](https://lib.findy.co.jp/organization/engineer-growth.md): How a team develops junior engineers through shared goals, frequent feedback, and staged learning, plus team study sessions and the mentor's role when AI agents write code. ## Developer Productivity - [What is developer productivity? Definition and levels](https://lib.findy.co.jp/productivity/why-measure.md): Explains the definition of developer productivity, the three levels of productivity with measurement and initiatives for each, why improvement matters, and cautions when pursuing it. ## AI Utilization - [What is vibe coding? Building software with an AI agent](https://lib.findy.co.jp/ai/vibe-coding.md): Building software in dialogue with an AI coding agent: the groundwork it requires, the verification that stays with the human, and how to write and sequence requests in an interactive session. - [What is context engineering? Designing what an agent reads](https://lib.findy.co.jp/ai/context-engineering.md): Designing everything an AI coding agent reads in a session: the instruction files loaded every time, and the material that accumulates as the work proceeds. - [What is an agentic workflow? Delegating implementation to AI](https://lib.findy.co.jp/ai/agentic-workflow.md): A delegation model where AI agents plan, implement, and verify on their own while humans set goals and judge the result, with context management at the core. - [What is a subagent? Delegating scoped tasks to agents](https://lib.findy.co.jp/ai/subagent.md): A subagent is a separate agent instance with its own context window, system prompt, and tool scope. A main agent delegates a scoped task to it and receives only the result. - [What is a skill? A reusable workflow unit for AI agents](https://lib.findy.co.jp/ai/skill.md): A skill packages a workflow into a directory of SKILL.md and supporting files that an AI agent loads on demand, so the same procedure runs reproducibly. - [What is MCP? Connecting AI agents to external tools](https://lib.findy.co.jp/ai/mcp.md): Model Context Protocol is an open standard that connects AI applications to external data sources, tools, and workflows. - [What is a plugin? One installable unit of agent setup](https://lib.findy.co.jp/ai/plugin.md): A plugin bundles custom commands, agents, skills, hooks, and MCP configuration into one distributable, versioned unit teams can install and update together. - [Security practices for running AI coding agents safely](https://lib.findy.co.jp/ai/security.md): Running a coding agent that reads untrusted text: prompt injection and where risk arises, least-privilege tool permissions, and keeping secrets out of the context. ## Frontend - [What is a testing strategy? Choosing the right test layer](https://lib.findy.co.jp/frontend/testing-strategy.md): Assign each verification to the lowest test layer that can catch its failure, using the Testing Trophy as the map of a frontend test suite. - [What is E2E testing? A small test suite you can trust](https://lib.findy.co.jp/frontend/e2e-testing.md): Protect primary user journeys with a small E2E suite that runs against a deployed environment and stays trustworthy. ## Backend - [How to choose the right database for your application](https://lib.findy.co.jp/backend/database-selection.md): How to decide which database holds your application's data: the strengths of relational, document, key-value, and warehouse types, and when to add a second one. - [How to improve database performance: read less storage](https://lib.findy.co.jp/backend/database-performance.md): The techniques of database performance work, explained as applications of a single principle: minimize storage reads. ## Mobile Apps - [How to choose a development approach for your mobile app](https://lib.findy.co.jp/mobile/technology-selection.md): Frames the mobile technology choice as a question of what you share: three categories by scope, four axes for choosing, and worked examples of the decision. ## DevRel - [The role of Developer Relations](https://lib.findy.co.jp/devrel/engineering-culture.md): Defines DevRel as a company's function for reaching developers, then covers engineering culture, the engineering community's three layers, and technical communication. > The links below point to documentation indexes. Follow each `/_llms/` index recursively until you reach documentation pages. ## Indexes - [Japanese (31 pages)](https://lib.findy.co.jp/_llms/ja.md): Documentation for Japanese. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.