求一个后端(Java、Python)的Claude.md

2026-04-11 13:070阅读0评论SEO资讯
  • 内容介绍
  • 文章标签
  • 相关推荐
问题描述:

求一个后端(Java、Python)的Claude.md
感谢佬~

网友解答:
--【壹】--:

蹲一个!


--【贰】--:

蹲一下!


--【叁】--:

牛的佬,抄作业了


--【肆】--:

## Repo Coding Conventions - Prefer `pydantic` models or `TypedDict`-style typed structures over passing raw untyped `dict` objects through the system. - Avoid `getattr` for normal application flow. Prefer explicit typed fields, dedicated adapter/helper methods, or small boundary objects. Reserve `getattr` for true dynamic interop boundaries such as plugin hooks, third-party SDK objects, or narrowly scoped test shims. - Prefer `class` + `@staticmethod` helper organization over scattered free functions when the logic belongs to a parser, loader, or service domain. - Reuse existing repository patterns and elegant implementations before introducing a new parsing or loading approach. - If a behavior, intent, or tradeoff is unclear, ask the user

阅读全文
标签:快问快答
问题描述:

求一个后端(Java、Python)的Claude.md
感谢佬~

网友解答:
--【壹】--:

蹲一个!


--【贰】--:

蹲一下!


--【叁】--:

牛的佬,抄作业了


--【肆】--:

## Repo Coding Conventions - Prefer `pydantic` models or `TypedDict`-style typed structures over passing raw untyped `dict` objects through the system. - Avoid `getattr` for normal application flow. Prefer explicit typed fields, dedicated adapter/helper methods, or small boundary objects. Reserve `getattr` for true dynamic interop boundaries such as plugin hooks, third-party SDK objects, or narrowly scoped test shims. - Prefer `class` + `@staticmethod` helper organization over scattered free functions when the logic belongs to a parser, loader, or service domain. - Reuse existing repository patterns and elegant implementations before introducing a new parsing or loading approach. - If a behavior, intent, or tradeoff is unclear, ask the user

阅读全文
标签:快问快答