refactor(handler): optimize mutual follow checks and remove unused skills

- remove unused .kilocode Go patterns and testing skill files
- simplify mutual follow status retrieval in post and user handlers
- restrict mutual follow status fetching to self-viewing scenarios to reduce unnecessary service calls

internal/handler/post_handler.go

@@ -102,14 +102,16 @@ func (h *PostHandler) GetByID(c *gin.Context) {
 	// 获取交互状态
 	isLiked, isFavorited := h.postService.GetPostInteractionStatusSingle(c.Request.Context(), id, currentUserID)
 
-	// 如果有当前用户，检查与帖子作者的相互关注状态
 	var authorWithFollowStatus *dto.UserResponse
-	if currentUserID != "" && post.User != nil {
-		_, isFollowing, isFollowingMe, err := h.userService.GetUserByIDWithMutualFollowStatus(c.Request.Context(), post.UserID, currentUserID)
-		if err == nil {
-			authorWithFollowStatus = dto.ConvertUserToResponseWithMutualFollow(post.User, isFollowing, isFollowingMe)
+	if post.User != nil {
+		if currentUserID != "" {
+			_, isFollowing, isFollowingMe, err := h.userService.GetUserByIDWithMutualFollowStatus(c.Request.Context(), post.UserID, currentUserID)
+			if err == nil {
+				authorWithFollowStatus = dto.ConvertUserToResponseWithMutualFollow(post.User, isFollowing, isFollowingMe)
+			} else {
+				authorWithFollowStatus = dto.ConvertUserToResponse(post.User)
+			}
 		} else {
-			// 如果出错，使用默认的author
 			authorWithFollowStatus = dto.ConvertUserToResponse(post.User)
 		}
 	}